Db2 11 for z/OS: Messages - IBM · 2021. 1. 13. · About this information. This information helps you to understand the messages that you could receive while working with Db2 11

Db2 11 for z/OS

Messages

IBM

GC19-4062-10

Notes

Before using this information and the product it supports, be sure to read the general information under"Notices" at the end of this information.

Subsequent editions of this PDF will not be delivered in IBM Publications Center. Always download thelatest edition from PDF format manuals for Db2 11 for z/OS (Db2 for z/OS Documentation Home).

2021-04-30 edition

This edition applies to Db2® 11 for z/OS® (product number 5615-DB2), Db2 11 for z/OS Value Unit Edition (productnumber 5697-P43), and to any subsequent releases until otherwise indicated in new editions. Make sure you are usingthe correct edition for the level of the product.

Specific changes are indicated by a vertical bar to the left of a change. A vertical bar to the left of a figure captionindicates that the figure has changed. Editorial changes that have no technical significance are not noted.© Copyright International Business Machines Corporation 1983, 2021.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/home/src/tpc/db2z_pdfmanuals.html

Contents

About this information .......................................................................................... vWho should read this information................................................................................................................vDb2 Utilities Suite for z/OS...........................................................................................................................vTerminology and citations........................................................................................................................... viAccessibility features for Db2 11 for z/OS..................................................................................................viHow to send your comments about Db2 for z/OS documentation........................................................... viiHow to interpret message numbers...........................................................................................................vii

Subcomponent identifiers....................................................................................................................viiiHow to find additional information about messages..................................................................................ix

Chapter 1. DSNA messages....................................................................................1

Chapter 2. DSNB messages.................................................................................. 43

Chapter 3. DSNE messages................................................................................ 121

Chapter 4. DSNF messages................................................................................ 159

Chapter 5. DSNG messages................................................................................161

Chapter 6. DSNH messages................................................................................165

Chapter 7. DSNI messages.................................................................................227

Chapter 8. DSNJ messages................................................................................ 249

Chapter 9. DSNL messages................................................................................ 329

Chapter 10. DSNM messages..............................................................................407

Chapter 11. DSNP messages.............................................................................. 411

Chapter 12. DSNQ messages.............................................................................. 429

Chapter 13. DSNR messages.............................................................................. 435

Chapter 14. DSNS messages.............................................................................. 455

Chapter 15. DSNT messages.............................................................................. 457

Chapter 16. DSNU messages.............................................................................. 619

Chapter 17. DSNV messages.............................................................................. 979

Chapter 18. DSNW messages........................................................................... 1013

Chapter 19. DSNX messages............................................................................ 1037

iii

Chapter 20. DSNY messages............................................................................ 1081

Chapter 21. DSNZ messages............................................................................ 1087

Chapter 22. DSN1 messages............................................................................ 1091






Appendix A. New, changed, and deleted messages........................................... 1203

Appendix B. z/OS diagnostic services...............................................................1205

Appendix C. Resource types.............................................................................1207

Appendix D. Service task plan names............................................................... 1213

Information resources for Db2 11 for z/OS and related products....................... 1215

Notices............................................................................................................1217Programming interface information......................................................................................................1218Trademarks............................................................................................................................................1218Terms and conditions for product documentation............................................................................... 1218Privacy policy considerations................................................................................................................1219

Glossary.......................................................................................................... 1221

iv

About this information

This information helps you to understand the messages that you could receive while working with Db2 11for z/OS (Db2 for z/OS). The topics provide detailed descriptions of the messages that are issued by Db2,with explanations and user responses for the situations that are associated with these messages.

Unless the message is issued by a subcomponent operating outside the Db2 environment, messages arepreceded by a command prefix that is defined during system installation. The command prefix is notshown in the message text.

Throughout this information, "Db2" means "Db2 11 for z/OS". References to other Db2 products usecomplete names or specific abbreviations.

Important: To find the most up to date content for Db2 11 for z/OS, always use IBM® Documentation ordownload the latest PDF file from PDF format manuals for Db2 11 for z/OS (Db2 for z/OS DocumentationHome).

This information assumes that Db2 11 is running in new-function mode, and that your application isrunning with the application compatibility value of 'V11R1', except for the following section that describethe migration process and how to activate new function:

• Migrating Db2 to Db2 11 (Db2 Installation and Migration)• What's new in Db2 11 (Db2 for z/OS What's New?)• Changes in Db2 11 (Db2 for z/OS What's New?)

Availability of new function in Db2 11

The behavior of data definition statements such as CREATE, ALTER, and DROP, which embed datamanipulation SQL statements that contain new capabilities, depends on the application compatibilityvalue that is in effect for the application. An application compatibility value of 'V11R1' must be ineffect for applications to use new capability in embedded statements such as SELECT, INSERT,UPDATE, DELETE, MERGE, CALL, and SET assignment-statement. Otherwise, an applicationcompatibility value of 'V10R1' can be used for data definition statements.

Generally, new SQL capabilities, including changes to existing language elements, functions, datamanipulation statements, and limits, are available only in new-function mode with applications set toan application compatibility value of 'V11R1'.

Optimization and virtual storage enhancements are available in conversion mode unless statedotherwise.

SQL statements can continue to run with the same expected behavior as in DB2® 10 new-functionmode with an application compatibility value of 'V10R1'.

Who should read this informationDb2 Messages lists messages issued by Db2, with explanations and suggested responses. Thisinformation is intended for users and system programmers who might encounter Db2 messages.

Db2 Utilities Suite for z/OSImportant: In Db2 11, the Db2 Utilities Suite for z/OS is available as an optional product. You mustseparately order and purchase a license to such utilities, and discussion of those utility functions in thispublication is not intended to otherwise imply that you have a license to them.

Db2 11 utilities can use the DFSORT program regardless of whether you purchased a license for DFSORTon your system. For more information, see the following informational APARs:

• II14047

© Copyright IBM Corp. 1983, 2021 v

https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/home/src/tpc/db2z_11_prodhome.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_migrdb2.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/wnew/src/tpc/db2z_11_wnew.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/wnew/src/tpc/db2z_whatschanged.html

• II14213• II13495

Db2 utilities can use IBM Db2 Sort for z/OS (5655-W42) as an alternative to DFSORT for utility SORT andMERGE functions. Use of Db2 Sort for z/OS requires the purchase of a Db2 Sort for z/OS license. For moreinformation about Db2 Sort for z/OS, see Db2 Sort for z/OS.

Related conceptsDb2 utilities packaging (Db2 Utilities)

Terminology and citationsWhen referring to a Db2 product other than Db2 for z/OS, this information uses the product's full name toavoid ambiguity.

The following terms are used as indicated:

Db2Represents either the Db2 licensed program or a particular Db2 subsystem.

IBM re-branded DB2 to Db2, and Db2 for z/OS is the new name of the offering previously know as"DB2 for z/OS". For more information, see Revised naming for IBM Db2 family products on IBM z/OSplatform. As a result, you might sometimes still see references to the original names, such as "DB2 forz/OS" and "DB2", in different IBM web pages and documents. If the PID, Entitlement Entity, version,modification, and release information match, assume that they refer to the same product.

Tivoli® OMEGAMON® XE for Db2 Performance Expert on z/OSRefers to any of the following products:

• IBM Tivoli OMEGAMON XE for Db2 Performance Expert on z/OS• IBM Db2 Performance Monitor on z/OS• IBM Db2 Performance Expert for Multiplatforms and Workgroups• IBM Db2 Buffer Pool Analyzer for z/OS

C, C++, and C languageRepresent the C or C++ programming language.

CICS®Represents CICS Transaction Server for z/OS.

IMSRepresents the IMS Database Manager or IMS Transaction Manager.

MVS™Represents the MVS element of the z/OS operating system, which is equivalent to the Base ControlProgram (BCP) component of the z/OS operating system.

RACF®Represents the functions that are provided by the RACF component of the z/OS Security Server.

Accessibility features for Db2 11 for z/OSAccessibility features help a user who has a physical disability, such as restricted mobility or limitedvision, to use information technology products successfully.

Accessibility featuresThe following list includes the major accessibility features in z/OS products, including Db2 11 for z/OS.These features support:

• Keyboard-only operation.• Interfaces that are commonly used by screen readers and screen magnifiers.

vi About this information

http://www.ibm.com/software/data/db2imstools/db2tools/db2-sort/

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utlpackaging.html

https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/899/ENUSLP18-0047/index.html

https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/899/ENUSLP18-0047/index.html

• Customization of display attributes such as color, contrast, and font size

Tip: IBM Documentation (which includes information for Db2 for z/OS) and its related publications areaccessibility-enabled for the IBM Home Page Reader. You can operate all features using the keyboardinstead of the mouse.

Keyboard navigationFor information about navigating the Db2 for z/OS ISPF panels using TSO/E or ISPF, refer to the z/OSTSO/E Primer, the z/OS TSO/E User's Guide, and the z/OS ISPF User's Guide. These guides describe how tonavigate each interface, including the use of keyboard shortcuts or function keys (PF keys). Each guideincludes the default settings for the PF keys and explains how to modify their functions.

Related accessibility information

IBM and accessibilitySee the IBM Accessibility Center at http://www.ibm.com/able for more information about the commitmentthat IBM has to accessibility.

How to send your comments about Db2 for z/OS documentationYour feedback helps IBM to provide quality documentation.

End of support (EOS): Db2 11 reached EOS on March 31, 2021. The online product documentation isprovided as-is for clients with extended service contracts. For more information, see End of support(March 31, 2021) (Db2 for z/OS Knowledge Center).

Send any comments about Db2 for z/OS and related product documentation by email [email protected].

To help us respond to your comment, include the following information in your email:

• The product name and version• The address (URL) of the page, for comments about online documentation• The book name and publication date, for comments about PDF manuals• The topic or section title• The specific text that you are commenting about and your comment

Related conceptsAbout this information (Db2 for z/OS Knowledge Center)Related referencePDF format manuals for Db2 11 for z/OS (Db2 for z/OS Documentation Home)

How to interpret message numbersDb2 issues messages to communicate system status and processing results. Messages are identifiable byunique message numbers. The format of a message number can help you understand what the messageapplies to and, in some cases, its severity.

Messages are identifiable by unique message numbers, which are eight to ten characters long. Messageidentifiers have the following format:DSNB209I

DSNThe first three characters are DSN, which is the Db2 component prefix.

BThe fourth character is the subcomponent identifier, which identifies the subcomponent of Db2 thatissued the message. Each subcomponent has an associated hexadecimal identifier (hex ID), which is

About this information vii

https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/home/src/tpc/db2z_11_prodhome.html

http://www.ibm.com/able

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/home/src/cmn/db2z_cmn_eos.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/home/src/cmn/db2z_cmn_eos.html

mailto:[email protected]

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/home/src/cmn/db2z_cmn_aboutinfo.html


the hexadecimal representation of the subcomponent identifier. In this example, B identifies the Db2buffer manager.

209The 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.

IThe last character of the message identifier is the message type code. Most Db2 messages use the Itype code, regardless of severity or whether an action is required.

Some older messages use other type codes. However, the type code does not necessarily reflect theseverity of these messages. Some messages use the following other type codes:A

Action is required immediately. The associated task does not continue until the requested actionis taken.

EAction is required eventually. However, the associated task continues. All RC=8 error messagesthat are not host related (SOFT errors) have the E changed to a W in precompiler output whenSQL(ALL) is in effect. All RC=8 errors (HARD errors) look the same as they have in the past.

Messages in some sub-components are associated with particular return codes. The return codes canvary by subcomponent. The introduction to each set of messages describes the return codes used for thatsubcomponent.

Messages are organized by subcomponent identifier and numeric identifier, and sorted numerically withineach group.

Related informationFormat of z/OS MVS system messages

Subcomponent identifiersThe identifiers for messages or reason codes in Db2 indicate the associated Db2 subcomponent orfunctional area.

The following table lists the Db2 subcomponents and functional areas and the identifiers that areassociated with each one. Some message identifiers are shared by more than one subcomponent orfunctional area. Also, subcomponents can call each other, so one subcomponent might return messageswith reason codes from another.

Table 1. Subcomponent identifiers used in messages and reason codes

Subcomponent or functionalarea

Associated identifier formessages

Associated identifier for reasoncodes

Call attachment facility and someDb2 supplied stored procedures

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'

viii About this information

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieam100/msgfmt.htm

Table 1. Subcomponent identifiers used in messages and reason codes (continued)

Subcomponent or functionalarea

Associated identifier formessages

Associated identifier for reasoncodes

IMS attachment facility M X'D4'

XML manager n/a X'D5'

Data space manager P X'D7'

MQListener Q n/a

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 supportsubcomponent

3 X'F3'

Group manager 7 X'F7'

Db2 Accessories Suite for z/OS 5 n/a

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 displayCICS messages. For information about CICS messages, see the information in the Search the CICSLibrary..

How to find additional information about messagesWhen you are working with Db2, you might encounter messages issued by other IBM products, such asIMS, CICS, or z/OS. Information about messages issued by these and other IBM products is available inIBM Documentation.CICS

Information for multiple versions of CICS are available as part of the CICS library. Search the CICSLibrary..

IMSIMS messages are available in IMS messages and codes.

IRLMMessages and codes related to the IRLM, which were previously part of Db2 Codes, are now providedin IRLM Messages and Codes for IMS and Db2 for z/OS. IRLM messages have the prefix dxr.

• IRLM return and reason codes (IRLM)• IRLM abend codes (IRLM)

About this information ix

http://www-01.ibm.com/support/knowledgecenter/search?scope=SSWHM2&scope=SS2L7A&scope=SSCLNZ&scope=SSPPUS&scope=SSPPVB&scope=SSPPU4&scope=SSQJMU&scope=SSBQNK&scope=SSB2L6&scope=SSZHFX&scope=SSZHJ2&scope=SSGMGV




http://www-01.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/common/mc.htm

http://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/irlm/src/tpc/irlm_codes.html

http://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/irlm/src/tpc/irlm_abendcodes.html

• DXR messages (IRLM)

z/OSInformation for multiple versions of z/OS is available as part of the z/OS library. Search the z/OSlibrary..

x Db2 11 for z/OS: Messages

http://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/irlm/src/tpc/irlm_messages.html

http://www-01.ibm.com/support/knowledgecenter/search?scope=SSLTBW

http://www-01.ibm.com/support/knowledgecenter/search?scope=SSLTBW

Chapter 1. DSNA messagesMessage identifiers that begin with DSNA communicate information about the call attachment facility(CAF).

DSNA messages fall into two categories:

• Messages that are written to a trace file. These are seen only if the trace is turned on (that is, ddnameDSNTRACE was allocated to SYSOUT or the TSO terminal).

• Messages that are returned by a Db2 stored procedure. These are seen only as a parameter that isreturned by the stored procedure.

DSNA messages use common elements and share the same basic structure:

• Message number (DSNAnnna).• The name of the CSECT responsible for writing the message.• TCB address of the task currently executing.• A series of tokens and token-explanations unique to each message.

The intent of these messages is to aid IBM Support. They contain information that might not bemeaningful except to IBM.

DSNA002E DSNACA00 TCB=address SYSTEMERROR - FOUND UNEXPECTEDTHREAD

ExplanationThe Db2 call attachment facility control block, theCAB, indicated that a thread was present when noneshould have been present. This is a CAF system error.

System actionThis message immediately precedes an 04E abend,with reason code 00C10002.

System programmer responseCollect a SYSUDUMP and DSNTRACE trace stream.

Programmer responseRefer the problem to your system programmer.

Problem determinationContact IBM Support.

DSNA201E DSNACA00 TCB=address CANNOTUSE 'CONNECT', ALREADYCONNECTED TO DB2

ExplanationA CONNECT request was received but a connection toDb2 already existed for the TCB identified by 'address'

in the message. This is a CAF error (applicationprogram error). The message is accompanied by returncode (R15) 200 and code (R0) 00C10201.

System actionNo new connection is made to Db2 and an error returnand reason code are issued. The Db2 call attachmentfacility is ready for more input.

System programmer responseRefer the problem to the programmer using the Db2call attachment facility.

Programmer responseYou must DISCONNECT the previous connectionbefore you can re-CONNECT. Correct the logic in yourcode.

Problem determinationSee a DSNTRACE trace stream to understand thecontext of this message.

DSNA202E DSNACA00 TCB=address CANNOTUSE 'OPEN', PRIOR OPEN OR SQLALREADY CONNECTEDAPPLICATION TO DB2

ExplanationAn OPEN request was received but a Db2 thread hadalready been created for the specified TCB. This is a

© Copyright IBM Corp. 1983, 2021 1

user error. The message is accompanied by returncode (R15) 200 and code (R0) 00C10202.

System actionNo new Db2 thread is created and an error return andreason code are issued. The Db2 call attachmentfacility is ready for more input.


Programmer responseYour application program had already (explicitly orimplicitly) established an OPEN level connection toDb2. You cannot do this again until the original OPEN isterminated. 'Explicit' OPENs occur when an applicationissues the call attachment facility OPEN request.'Implicit' OPENs occur when an application issues SQLstatements before a Db2 connection was established.Correct the logic in your application program.


DSNA203E DSNACA00 TCB=address CANNOTUSE 'CLOSE', THERE WAS NO'OPEN' IN EFFECT

ExplanationA CLOSE request was received but no OPEN levelconnection (implicit or explicit) existed for this task.This is a user error. The message is accompanied byreturn code (R15) 200 and code (R0) 00C10203.

System actionNo CLOSE is performed. The Db2 call attachmentfacility is ready for more input.


Programmer responseCorrect the logic in your application. Do not issueCLOSE unless an explicit OPEN has been performed.'Explicit' OPENs occur when an application issues thecall attachment facility OPEN request.


DSNA204E DSNACA00 TCB=address CANNOTUSE 'DISCONNECT', THERE WASNO 'CONNECT' IN EFFECT

ExplanationA DISCONNECT request was received but no Db2connection had been established. This is a user error.The message is accompanied by return code (R15)200 and code (R0) 00C10204.

System actionNo DISCONNECT has been performed. The Db2 callattachment facility is ready for more input.


Programmer responseCorrect the logic in your application. Do not issueDISCONNECT unless a CONNECT has been performed.


DSNA205E DSNACA00 TCB=address CANNOTUSE 'TRANSLATE', THERE WAS NOCONNECTION TO DB2 ORNOTHING TO TRANSLATE

ExplanationA TRANSLATE request was received but no data wasavailable for translation. You must have valid Db2 callattachment facility control structures before you canmake a TRANSLATE request. Control structures arebuilt when you issue explicit or implicit connectionrequests. This is a user error. The message isaccompanied by return code (R15) 200 and code (R0)00C10205.

System actionNo TRANSLATE is performed. The Db2 call attachmentfacility is ready for more input.

2 Db2 11 for z/OS: Messages


Programmer responseCorrect the logic in your application. Do not issueTRANSLATE unless a Db2 connection has beenattempted.


DSNA206E DSNACA00 TCB=address WRONGNUMBER OF PARMS OR VL BITOFF

ExplanationAn erroneous Db2 call attachment facility request wasreceived. The request had too many or too fewparameters and could not be processed. The messageis accompanied by return code (R15) 200 and code(R0) 00C10206.

System actionThe previous request was not processed. The Db2 callattachment facility is ready for more input.


Programmer responseCorrect the logic in your application. Be sure that anyparameter list passed to the Db2 call attachmentfacility has the correct number of parameters for theindividual call, and that the high order (VL) bit is turnedon to end the parameter list.


DSNA207E DSNACA00 TCB=tcb-address DIDNOT RECOGNIZE ACTIONPARAMETER - parameter-name

ExplanationAn unrecognized action request type or parameter wasreceived by the Db2 call attachment facility and could

not be processed. The allowable action request typesare CONNECT, OPEN, CLOSE, DISCONNECT, andTRANSLATE. This message is accompanied by returncode (R15) 200 and code (R0) 00C10207.

System actionControl returns to the caller. Your request was notprocessed. The Db2 call attachment facility is ready formore input.


Programmer responseCorrect the logic in your application. Check the spellingof the action parameter type or keyword on theprevious request passed to the Db2 call attachmentfacility. The action parameter type you passed is listedin the parm field of the DSNA800I trace message. Ifthe error is not the action parameter, the parameter inerror is listed in the parm field of this message.


Related tasksInvoking the call attachment facility (Db2Application programming and SQL)Related referenceCAF return codes and reason codes (Db2Application programming and SQL)Related information00C10207 (Db2 Codes)

DSNA208E DSNACA00 TCB=address CANNOTHAVE 2 SSIDS (ssid1 AND ssid2)FROM 1 TCB

ExplanationAn OPEN request was received specifying a differentsubsystem identifier (ssid2) than the previousCONNECT request (ssid1). Your task can only beconnected to a single Db2 subsystem. The message isaccompanied by return code (R15) 200 and code (R0)00C10208.

System actionControl returns to the caller. Your request was notprocessed. The Db2 call attachment facility is ready formore input.

Chapter 1. DSNA messages 3

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_invokecaf.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_invokecaf.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_cafreturnreasoncodes.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_cafreturnreasoncodes.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00c10207.html


Programmer responseSpecify the correct Db2 subsystem identifier on boththe OPEN and CONNECT requests.


DSNA209E DSNACA00 A STOREDPROCEDURE ISSUED AN EXPLICITCALL TO DSNALI

ExplanationA stored procedure issued an explicit call to DSNALI.This is not allowed. Return code 200 in register 15 andcode 00C10209 in register 0 accompany this message.

System actionControl returns to the caller. The request was notprocessed. The Db2 call attachment facility is ready formore input.


Programmer responseRemove explicit calls to DSNALI from the applicationprogram.

Problem determinationSee a DSNTRACE trace job stream to understand thecontext of this message.

DSNA301I THE VALUE parm-value FORPARAMETER parm-name IS NOTVALID

ExplanationThe stored procedure DSNACICS could not runbecause one of the input parameters contains anincorrect value.

System actionThe stored procedure DSNACICS terminates withoutcalling the CICS transaction.

System programmer responseEnsure that the user exit DSNACICX sets theparameter to a valid value.

Programmer responseCorrect the input parameter value specified on the SQLCALL statement.

Severity12

DSNA302I THE REQUIRED INPUTPARAMETER parm-nameCONTAINS NULLS

ExplanationThe stored procedure DSNACICS could not runbecause one or more of the required input parameterscontains a null value.


System programmer responseEnsure that the user exit DSNACICX sets theparameter to a non-null value.

Programmer responseCorrect the input parameter value in the SQL CALLstatement, or ensure that the user exit DSNACICX setsthe parameter to a non-null value.

Severity12

DSNA303I THE PARAMETER NETNAME WASNOT SPECIFIED WHEN THECONNECT TYPE OF SPECIFIC WASSPECIFIED

ExplanationThe input parameter NETNAME must contain a non-null value when the CONNECT TYPE parameter is setto SPECIFIC.



System programmer responseEnsure that the user exit DSNACICX sets theparameter to a non-null value.

Programmer responseCorrect the input parameter value in the SQL CALLstatement, or ensure the user exit DSNACICX sets theparameter to a non-null value.

Severity12

DSNA304I THE USER EXIT DSNACICXRETURNED RETURN CODE =X'hhhhhhhh' AND THEFOLLOWING ERROR MESSAGE:

ExplanationThe user exit DSNACICX returned a non-zero returncode and a message to stored procedure DSNACICS.The message that DSNACICX returns immediatelyfollows message DSNA304I.


System programmer responseCorrect the cause of the error message that the userexit generated.

Programmer responseContact the system programmer.

Severity12

DSNA305I THE CICS EXCI func REQUESTFAILED. CICS RESPONSE CODE =X'hhhh' CICS REASON CODE =X'hhhhhhhh'

ExplanationDSNACICS uses the CICS EXCI Call interface torequest the execution of a CICS server program. CICS

EXCI interface call func resulted in an unexpectedCICS response code and reason code. Possible valuesof func are:Initialize_User

Initializes the EXCI user environment.Allocate_Pipe

Allocates a session to a CICS region.Open_Pipe

Connects an allocated pipe to a receive session ofthe CICS region.

DPL_RequestIssues a request to execute the CICS serverprogram.

Close_PipeDisconnects an open pipe from a CICS region.

Deallocate_PipeDeallocates a pipe from a CICS region.

The failure can occur because the EXCI interface is notproperly enabled for the CICS subsystem. Forexplanations of the CICS response code and reasoncode, see CICS Transaction Server for z/OS ExternalInterfaces Guide.


System programmer responseEnsure that the EXCI interface is enabled to the CICSregion that the stored procedure calls. If you suspectan error in the Db2 stored procedure, you might needto report the problem. For information aboutidentifying and reporting the problem, see Collectingdiagnostic data (Collecting data).

Add a DSNDUMP DD statement to the JCL startupprocedure for the stored procedure address space inwhich DSNACICS runs. Then rerun the application thatcalls DSNACICS. This causes Db2 to generate an SVCdump whenever it issues an error message forDSNACICS.

If you suspect an error in the Db2 stored procedure,you might need to report the problem. For informationabout identifying and reporting the problem, seeCollecting diagnostic data (Collecting data).Collect thefollowing diagnostic items:

• Console output from the system on which the jobwas run, and a listing of the SYSLOG data set for theperiod of time that spans the failure.

• Dynamic dump, taken to SYS1.DUMPxx data set, byDb2 (04E and 04F abends).

• CICS trace listing.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_collectingdata4db2zos.html




Severity12

DSNA306I THE CICS SERVER PROGRAMprogram ABENDED. CICS ABENDCODE=C'cccc'

ExplanationThe CICS server program that DSNACICS calledabnormally terminated. CICS returns a four-characterabend code to indicate the error. These error codes aredescribed in CICS Transaction Server for z/OS ProblemDetermination Guide.

System actionStored procedure DSNACICS processes the nextrequest. CICS does a backout to the last syncpoint andforces the SYNCONRETURN option.

System programmer responseCorrect the cause of the error in the server program.Ensure that the mirror transaction is still enabled afterthis error. The mirror transaction must be enabled sothat subsequent requests to run a server program areaccepted.

Programmer responseCorrect the error in the server program.

Severity12

DSNA307I z/OS token-service REQUESTFAILED. SYSTEM RETURNCODE=X'hhhh'

ExplanationDSNACICS uses the z/OS token services to save task-level information. The z/OS service returned anunexpected return code.

token-service is the token service function thatDSNACICS requested. Possible values are:Create_token

Create a token using the IEANTCR service.Retrieve_token

Retrieve a token using the IEANTRT service.

See the description of IEANTCR or IEANTRT in z/OSMVS Programming: Assembler Services Reference,Volumes 1 and 2 for a full description of the returncode.

System actionStored procedure DSNACICS processes the nextrequest.

System programmer responseAdd a DSNDUMP DD statement to the JCL startupprocedure for the stored procedure address space inwhich DSNACICS runs. Then rerun the application thatcalls DSNACICS. This causes Db2 to generate an SVCdump whenever it issues an error message forDSNACICS.






Severity12

DSNA308I THE CICS EXCI DPL_REQUESTREQUEST FAILED. CICSRESPONSE CODE=0. DPLRETAREA CONTAINSFIELD1=X'hhhhhhhh',FIELD2=X'hhhhhhhh',FIELD3=C'cccc'

ExplanationDSNACICS uses the CICS EXCI Call interface torequest the execution of a CICS server program. TheDPL_REQUEST command returned an unexpectedvalue in the DPL_RETAREA. See CICS TransactionServer for z/OS External Interfaces Guide and CICSApplication Programming Guide for a full description ofthe meanings of FIELD1, FIELD2, and FIELD3.



System actionStored procedure DSNACICS processes the nextrequest.

System programmer responseAdd a DSNDUMP DD statement to the JCL startupprocedure for the stored procedure address space inwhich DSNACICS runs. Then rerun the application thatcalls DSNACICS. This causes Db2 to generate an SVCdump whenever it issues an error message forDSNACICS.





Programmer responseCorrect any errors in the server program. Contact thesystem programmer.

Severity12

DSNA309I UNABLE TO LOAD USER EXITDSNACICX. SYSTEM REASONCODE=X'hhhh' SYSTEMCOMPLETION CODE=X'hhhh'

ExplanationDSNACICS was unable to load the user exit routineDSNACICX.

System actionThe stored procedure DSNACICS does not call theCICS transaction. DSNACICS processes the nextrequest.

System programmer responseEnsure that the STEPLIB statement in the startupprocedure for the stored procedure address spacespecifies the library that contains DSNACICX. A defaultuser exit is shipped in the SDSNLOAD Db2 library.







Severity12

DSNA310I STORED PROCEDURE TASKCANCELLED BY OPERATOR

ExplanationThe task that called the DSNACICS stored procedurewas canceled by the operator.

System actionDSNACICS terminates immediately. The CICS serverprogram might have been called.

System programmer responseDetermine why the operator canceled the storedprocedure task.


Severity12

DSNA311I DSNACICS ABNORMALLYTERMINATED




ExplanationThe task that called the DSNACICS stored procedureabnormally terminated.

System actionDSNACICS terminates immediately. The CICS serverprogram might have been called. An SVC dump or aSYSMDUMP is generated for this error. If a CICSservice encountered an error, a SYSMDUMP might begenerated. For an abend in the stored procedure, anSVC dump is generated.

System programmer responseReview the JES messages for the stored procedureaddress space in which DSNACICS runs. Look for CICSor system messages that describe the source of theproblem.

If you suspect an error in Db2, you might need toreport the problem. For information about identifyingand reporting the problem, see Collecting diagnosticdata (Collecting data).Collect the following diagnosticitems:





Severity12

DSNA312I USER EXIT DSNACICXABNORMALLY TERMINATED

ExplanationUser exit program DSNACICX abnormally terminated.

System actionDSNACICS terminates immediately. The CICS serverprogram is not called. An SVC dump is generated forthis error.

System programmer responseDetermine why the user exit abended. If you suspectan error in Db2, you might need to report the problem.

For information about identifying and reporting theproblem, see Collecting diagnostic data (Collectingdata).. Collect the following diagnostic items:





Severity12

DSNA313I DSNACICS TERMINATED BY atDB2 CANCEL THREAD COMMAND

ExplanationThe stored procedure DSNACICS terminated becausethe operator issued the at Db2 CANCEL THREADcommand.

System actionDSNACICS terminates immediately. The CICS serverprogram might have been called.

System programmer responseDetermine why the operator issued the at Db2 CANCELTHREAD command.


Severity12

DSNA314I UNABLE TO LOAD CICS STUBROUTINE DFHXCSTB. SYSTEMREASON CODE=X'hhhh' SYSTEMCOMPLETION CODE=X'hhhh'

ExplanationDSNACICS was unable to load the CICS stub routineDFHXCSTB.






System actionThe stored procedure DSNACICS does not call theCICS transaction. DSNACICS processes the nextrequest.

System programmer responseEnsure that the STEPLIB statement in the startupprocedure for the stored procedure address spacespecifies the CICS library that contains DFHXCSTB.DFHXCSTB is in the CICS EXCI library (SDFHEXCI).This library must be APF authorized.


If you suspect an error in Db2, you might need toreport the problem. For information about identifyingand reporting the problem, see Collecting diagnosticdata (Collecting data). Collect the following diagnosticitems:





Severity12

DSNA315I stored-procedure FUNCTION func-name HAS COMPLETEDSUCCESSFULLY.

ExplanationThe stored procedure, stored-procedure, executedsuccessfully.

System actionNone.

Programmer responseNone.

DSNA316I stored-procedure INPUTPARAMETER ERROR. CALLERMUST PROVIDE INPUT FORPARAMETER parm-name WITHFUNCTION func-name.

ExplanationA value for parameter parm-name is required forfunction func-name.

System actionThe execution of the stored procedure, stored-procedure, terminated before invoking IMS.

Programmer responseProvide an appropriate value for the parameter, andre-run the function.

DSNA317I stored-procedure ERROR INotmaci-api API. RC=return-code,RSN1=reason-code1,RSN2=reason-code2,RSN3=reason-code3,RSN4=reason-code4.

ExplanationOTMA Callable Interface API otmaci-api encounteredan error.


Programmer responseRefer to the IMS OTMA Guide and Reference forexplanations of the return and reason codes.

DSNA318I stored-procedure ERROR IN RRSCTXRCC API. RC=return-code

ExplanationAn error was encountered in RRS when processing thetwo-phase commit.





Programmer responseRefer to the MVS Programming Resource Recoverymanual for an explanation of the return code.

DSNA319I stored-procedure RECEIVEDUNKNOWN FUNCTION func-name

ExplanationThe stored procedure, stored-procedure, received anunknown function name in parameter 1 of the storedprocedure call.

System actionThe stored procedure terminated before invoking IMS.

Programmer responseSpecify a function name known to the storedprocedure in parameter 1.

DSNA320I DSNAIMS ERROR IN CTXSWCHDURING THE SWITCH AWAY FROMPRIVATE CONTEXT. RC=return-code

ExplanationAn error was encountered in CTXSWCH API during theswitch away from private context of DSNAIMS.

System actionDSNAIMS is terminated after executing CTXSWCH.

Programmer responseContact IBM service for the return code.

DSNA321I DSNAIMS ERROR IN CTXSWCHDURING THE SWITCH TO PRIVATECONTEXT. RC=return-code

ExplanationAn error was encountered in CTXSWCH API during theswitch to private context of DSNAIMS.

System actionDSNAIMS is terminated after executing CTXSWCH.

Programmer responseContact IBM service for the return code.

DSNA601I csect-name THE PARAMETERparm-name IS NOT VALID,

INVALID REASON CODE = reason-invalid

ExplanationThe parameter specified in the message is not valid.parm-name

The name of the parameter that contained aninvalid value.

reason-invalidThe reason that the parm-name parameter value isnot valid:

1. The value is not acceptable.2. The value is not unique.3. The value is null.4. The value is blank.5. The value is not null.6. The length of the value is not valid.7. The parm-name parameter is not known.8. The parm-name parameter is missing.

The specified parameter is not valid for the indicatedreason:

The csect-name in the message identifies the CSECTthat issued the message.

System actionThe stored procedure, started task, or batch programterminates.

Programmer responseCorrect the input parameter value specified on the SQLCALL statement or on the start command.

Severity12 (severe)

DSNA602I csect-name INCORRECT DSNSUBCOMMAND subcommandRECEIVED

ExplanationThe DSN subcommand specified is not an acceptablevalue. The only supported DSN subcommands are:BIND, REBIND and FREE.

System actionProcessing terminates.


Programmer responseCorrect the invalid DSN subcommand.

Severity12 (severe)

DSNA603I csect-name THE COLUMN column-name IN TABLE table-name IS NOTVALID. row-identifier=row-id.INVALID REASON CODE= reason-code

ExplanationAn invalid value was supplied for column-namecolumn.

csect-nameThe name of the control section that issued themessage.

column-nameThe name of the column.

table-nameThe name of the table.

row-identifier=row-idIndicates the row that contains the invalid column.

reason-codeA numeric value that indicates that reason that thespecified column is not valid:1

The value is not an acceptable value.2

The length of the value is invalid.3

The value is null.


User responseSpecify a valid value for the specified column.

Severity12 (severe error)

DSNA604I csect-name DUPLICATE OBJECT-ID object-id IN TABLE table-name

ExplanationA duplicate value was supplied for the object IDcolumn in table-name table. The duplicate value wasin the row with object ID object-id .


User responseSpecify a unique object-id for the object ID column inthe named table.

Severity12 (severe)

DSNA605I csect-name THERE ARE object-numOBJECTS NOT FOUND IN THE DB2CATALOG

ExplanationThere are object-num objects not found in the Db2catalog.

System actionObjects not found in the Db2 catalog are notprocessed.

User responseVerify the name of the objects that were notprocessed.

Severity12 (severe)

DSNA606I csect-name UNABLE TO data-set-action DATA SETDSNAME=dsname, MVS macnameMACRO FAILED WITH RETURNCODE=xx

ExplanationAn MVS non-VSAM macro returned an unexpectedreturn code when it was invoked.


System actionProcessing of the specified data set terminates.


Programmer responseSpecify valid credentials in the SQL CALL statement. Ifthe problem persists, ask your security administratorto check the security configuration for the specifieduser.

Refer to z/OS DFSMS: Macro Instructions for Data Setsfor more information on the MVS RETURN CODEassociated with the failed MVS non-VSAM macro.

Severity12 (severe)

DSNA607I csect-name UNABLE TO member-action MEMBER= member OF DATASET DSNAME= dsname, MEMBERNOT FOUND

ExplanationThe action on the library member failed because thelibrary member was not found.


User responseSpecify a valid library for member-name.

Severity12 (severe)

DSNA608I csect-name UNABLE TO member-action MEMBER=member OF DATASET DSNAME=dsname, MVSmacname MACRO FAILED WITHRETURN CODE=xx

ExplanationAn MVS non-VSAM macro returned an unexpectedreturn code when it was invoked. The 'csect-name' inthe message identifies the CSECT that issued themessage.

System actionProcessing of the specified library member terminates.

User responseRefer to z/OS DFSMS: Macro Instructions for Data Setsfor more information on the MVS RETURN CODEassociated with the failed MVS non-VSAM macro.

Severity12 (severe)

DSNA609I csect-name UNABLE TO SUBMIT AJOB FOR EXECUTION, MVSmacname MACRO FAILED WITHRETURN CODE=xx

ExplanationAn error occurred when an MVS non-VSAM macro toopen, write, or close the internal reader was called towrite a complete job to the internal reader. The 'csect-name' in the message identifies the CSECT that issuedthe message.


User responseRefer to z/OS DFSMS: Macro Instructions for Data Setsfor more information on the MVS RETURN CODEassociated with the failed MVS non-VSAM macro.

Severity12 (severe)

DSNA610I csect-name INSUFFICIENT RACFAUTHORITY FOR DATA SET

ExplanationA RACF error was encountered while processing a dataset.

System actionProcessing the data set terminates.

User responseContact the system programmer, or systemadministrator to arrange for the required RACF orequivalent security authorization. If more informationis needed, look at the messages in the console log.

Severity12 (severe)

DSNA611I csect-name THE data-set-attributeOF THE DATA SETDSNAME=dsname IS NOT yy


ExplanationThe data set indicated in the message cannot beprocessed because the data set attribute is notsupported.

System actionNo action is taken with the named data set.

Programmer responseSpecify a data set with the correct data set attribute.

Severity12 (severe)

DSNA612I csect-name INSUFFICIENT SPACEFOR DATA SET

ExplanationInsufficient disk space was encountered while writingto a data set.

System actionProcessing of the data set terminates.

Programmer responseAllocate more space for the data set. If moreinformation is needed, look at the messages in theconsole log.

Severity12 (severe)

DSNA613I csect-name THE DATA SET NAMEDSNAME=dsname MUST NOTBEGIN WITH A PATTERNMATCHING CHARACTER

ExplanationThe specified data set name begins with an '*' or '%'.This is not allowed for filtering, because it will cause amassive search of the catalog and could tie up a lot ofsystem resources.

System actionNo action is taken with the named data set.

Programmer responseCorrect the invalid data set name.

Severity12 (severe)

DSNA614I csect-name UNABLE TO OBTAINstorage-usage STORAGE, SIZE =size BYTES

ExplanationAn error occurred when the stored procedure or batchprogram attempted to obtain size bytes of storage forthe storage-usage indicated. The csect-name in themessage identifies the CSECT that issued themessage.

System actionThe stored procedure or batch program terminates.

Programmer responseNotify the system programmer before attempting toreissue the SQL CALL statement or run the batchprogram again.

Severity12 (severe)

DSNA615I csect-name UNABLE TO LOADmodule-name MODULE, LOADR15=rc

ExplanationAn error resulted when an attempt was made to loadthe module indicated in the message.


System programmer responseVerify that the named load module exists, and thatDb2 can access it.

Programmer responseNotify the system programmer.

Severity12 (severe)

DSNA616I csect-name CATALOG SEARCHINTERFACE ERROR, R15=xx,REASON CODE= yy RETURNCODE=zz


ExplanationAn error occurred when the Catalog Search Interface(CSI) was called.


Programmer responseAnalyze the R15 reason code and return code values,and take the appropriate action.

Severity12 (severe)

Related informationhttp://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxbd00/toc.htm

DSNA617I csect-name IFCA ERROR,IFCARC1=ifcarc1-value,IFCARC2=ifcarc2-value,IFCABNM=ifcabnm-value,IFCAGRSN=ifcagrsn-value,IFCAGBNM=ifcagbnm-value

ExplanationAn error occurred when submitting a Db2 commandthrough the instrumentation facility interface (IFI).Tokens in the message indicate values of fields in theIFI Communication Area (IFCA):ifcarc1-value

The X'E6......' return code value, from the IFCARC1field.

ifcarc2-valueThe X'E6......' reason code value, from the IFCARC2field.

ifcabnm-valueThe number of bytes that did not fit in the returnarea, from the value of the IFCABNM field.

ifcagrsn-valueReason code for the situation in which an IFI callsrequests data from members of a data sharinggroup, and not all the data is returned from groupmembers, from the IFCAGRSN field.

ifcagbnm-valueTotal length of data that was returned from otherdata sharing group members and did not fit in thereturn area, form the IFCAGBNM field.


Programmer responseTo diagnose the error, refer to the reason codes, andother IFCA field values that accompany the messageto determine the cause of the error.


Related conceptsX'E6......' codes (Db2 Codes)Related referenceInstrumentation facility communications area(IFCA) (Db2 Performance)

DSNA618I csect-name SQL ERROR DURINGSQL STATEMENT sql-statement,object-type = object-name

ExplanationAn SQL error resulted when the stored procedureissued an SQL statement for the indicated Db2 object.


sql-statementThe SQL statement that encountered the error.

object-typeThe type of Db2 object that the failed SQLstatement is processing.

object-nameThe name of the Db2 object that the failed SQLstatement is processing

System actionThe stored procedure that issued the SQL statementterminates.

Information is written to the SQLCA. The informationcan be either:

• A formatted form of the SQLCA and a text messagethat is based on the SQLCODE field of the SQLCA.

• An unformatted form of the SQLCA.

Programmer responseLocate the additional information that is written to theSQLCA and take the appropriate action or actions.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxbd00/toc.htm



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_00e6.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_ifca.html


Related conceptsSQL error codes (Db2 Codes)

DSNA619I csect-name SUBSYSTEMINTERFACE ERROR, FUNCTIONCODE=n, RETURN CODE=xx,SSOBRETN=yy, additional-info

ExplanationAn error occurred when a subsystem interface (SSI)function was called. The 'csect-name' in the messageidentifies the CSECT that issued the message. The SSIfunction codes are:

• 54 - Request subsystem version information call• 79- SYSOUT Application Program Interface• 80 - Extended status function call


Programmer responseRefer to z/OS DFSMS: Macro Instructions for Data Setsfor more information on the MVS RETURN CODEassociated with the failed MVS non-VSAM macro.

Severity12 (severe)

DSNA620I csect-name ERROR ALLOCATINGDATA SET DSNAME=dsname,RETURN CODE=xx, ERRORREASON CODE=yy, INFO REASONCODE=zz

ExplanationAn error occurred when the DYNALLOC macro wasinvoked to dynamically allocate the named data set.


User responseAnalyze the DYNALLOC RETURN CODE, error reasoncode, and the informational reason code values, andtake the appropriate action.

Severity12 (severe)

Related referenceInterpreting DYNALLOC return codes (MVSProgramming Authorized Assembler ServicesReference)

DSNA621I csect-name ATTEMPT TOPERFORM RRS ATTACH FUNCTIONfuncname FAILED, RRS ATTACHRC=rc, RETCODE=return-codeREASCODE=reason-code

ExplanationRRSAF returned an unexpected return code when itwas called to connect to Db2.


User responseTake the appropriate action for the specified RRSAFattach, return, and reason codes.

Severity12 (severe)

Related conceptsRRSAF return codes and reason codes (Db2Application programming and SQL)Related tasksInvoking the Resource Recovery Servicesattachment facility (Db2 Applicationprogramming and SQL)Controlling RRS connections (Db2Administration Guide)

DSNA622I csect-name THE function-nameFUNCTION CALL ISUNSUCCESSFUL, reason

ExplanationA z/OS C/C++ function returned an error.


function-nameThe name of the z/OS C/C++ function.

reasonThe run time error message string thatcorresponds to the error code errno, followed bythe errno2 value. (errno and errno2 are z/OS C/C++function error code values.)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_n.html

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa800/dynrtcd.htm



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_rrsafreturnreasoncodes.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_invokerrsaf.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_controlrrsconnections.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_controlrrsconnections.html


User response:See the information about z/OS XL C/C++ run timelibrary functions for descriptions of the error codesand take the appropriate action.


Related referencez/OS XL C/C++ runtime library functions (C/C++Run-Time Library Reference)

DSNA623I csect-name THE PROCEDUREprocedure-name DID NOTCOMPLETE SUCCESSFULLY,RETURN CODE=xx

ExplanationThe procedure procedure-name did not completesuccessfully when it was internally invoked, returningthe indicated return code value. This message isfollowed by the error message returned by the namedprocedure, if applicable.


User responseReview the error message returned by the namedstored procedure.

Severity12 (severe)

DSNA624I csect-name THE STOREDPROCEDURE ABENDED

ExplanationThe stored procedure abended and did not completesuccessfully.


User responseReport the problem to IBM Support.

Severity12 (severe)

DSNA625I csect-name THE STOREDPROCEDURE TASK WASTERMINATED BY THE OPERATOR

ExplanationThe stored procedure did not complete successfully,because it was terminated by the operator.


User responseIssue the SQL CALL statement again.

Severity12 (severe)

DSNA626I csect-name THE function-nameFUNCTION CALL ISUNSUCCESSFUL, parameter-name=parameter-value, reason

ExplanationA z/OS C/C++ function or a TSO/E function returned anerror when the specified parameter value was passedto the function.


function-nameThe name of the z/OS C/C++ or TSO/E function.

parameter-nameThe name of the function parameter.

parameter-valueThe value of the function parameter.

reasonFor z/OS C/C++ functions, reason is the run timeerror message string that corresponds to the errorcode errno, followed by the errno2 value. (errnoand errno2 are z/OS C/C++ function error codevalues.)

For TSO/E functions, reason can be one of thefollowing values:

• If function-name is LISTDSI, reason is theLISTDSI reason code (SYSREASON).

• If function-name is SYSDSN, reason is themessage that is returned by SYSDSN.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxbd00/keyword.htm



User responseFor z/OS C/C++ functions, see the information aboutz/OS XL C/C++ run time library functions fordescriptions of the error codes and take theappropriate action.

For TSO/E functions, see the information aboutLISTDSI and SYSDSN for descriptions of the TSO/Efunction errors and take the appropriate action.


Related referencez/OS XL C/C++ runtime library functions (C/C++Run-Time Library Reference)LISTDSI (TSO/E REXX Reference)SYSDSN (TSO/E REXX Reference)

DSNA627I csect-name THE funcnameFUNCTION CALL ISUNSUCCESSFUL, RETURN CODE=xx, ERROR REASON CODE=yy,INFO REASON CODE=zz

ExplanationA z/OS C/C++ function returned an unexpected returncode. The 'csect-name' in the message identifies theCSECT that issued the message. The possible namesof the z/OS C/C++ function are:

• dynalloc(): Allocate a data set• dynfree(): Deallocate a data set

An error occurred when a subsystem interface (SSI)function was called. The 'csect-name' in the messageidentifies the CSECT that issued the message. The SSIfunction codes are:

• 54 - Request subsystem version information call• 79- SYSOUT Application Program Interface• 80 - Extended status function call

System actionIf the function name is dynalloc(), then processingterminates.

Programmer responseRefer to z/OS DFSMS: Macro Instructions for Data Setsfor information on the DYNALLOC RETURN CODE,

ERROR REASON CODE, and INFO REASON CODEvalues.

Severity12 (severe) if the function name is dynalloc(). If thefunction name is dynfree(), then the Severity is thedynfree() return code.

DSNA628I csect-name THE program-typeprogram-name ENCOUNTERED ANERROR WHILE USING THEEXTENDED MCS CONSOLE TOISSUE THE MVS SYSTEMCOMMAND command-name.additional-information

ExplanationThe stored procedure encountered an error when itattempted to activate the extended MCS console orretrieve messages that are queued to the extendedMCS console.


program-type

The type of application that issued the MVS systemcommand: BATCH PROGRAM or STOREDPROCEDURE

program-name

The name of the batch program or storedprocedure.

command-nameThe system command that was issued.

additional-informationA string that provides more details about thereason for the message.


Programmer responseFor each of the macros that are described inadditional-information, look up the associated returnand reason codes in the MVS Programming AuthorizedAssembler Services information.

Related referenceMVS Programming: Authorized AssemblerServices Reference SET-WTO




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/ldsi.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/ikja30047.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa400/toc.htm


DSNA629I csect-name THE PARAMETERparm-name RETURNED BY THESTORED PROCEDURE proc-nameIS NOT VALID. INVALID REASONCODE=xx

ExplanationAn invalid value was returned by the indicatedprocedure for the specified parameter. The cause ofthe invalid error is identified by the invalid reason codevalue in the message text. The specified parameter isnot valid for the indicated reason:3

Value is null.


User responseReport the problem to IBM Support.

Severity12 (severe)

DSNA631I csect-name THE jes-versionCOMMAND command WAS ISSUEDBUT NOT ACCEPTED

ExplanationThe command response received does not indicatewhether the command was accepted or completed.The 'csect-name' in the message identifies the CSECTthat issued the message. The possible commands are:

• CANCEL - Cancel a job• PURGE - Purge a job

System actionProcessing completes. The RETURN_CODE outputparameter is 8 if the command was issued by a storedprocedure.

User responseIssue the JES2 command $D JOB or the JES3command *INQUIRY,J to display the current status ofthe job.

Severity8 (error)

DSNA632I csect-name JOB SUBMISSIONFAILED

ExplanationAn error occurred while submitting a job for execution.A job identifier was not returned when the ENDREQmacro was issued after a complete job was written tothe internal reader. The 'csect-name' in the messageidentifies the CSECT that issued the message.


User responseReview the submitted JCL records to ensure that it hasa valid JOB statement.

Severity12 (severe)

DSNA634I csect-name THE JES-MANAGEDSYSOUT DATA SET IS EMPTY,JOBID=jobid

ExplanationA request was made to process SYSOUT data setsresiding on JES spool for the indicated job identifierspecified. However, the indicated job does not haveany SYSOUT data sets.

System actionNo action is taken with the specified job identifier.

User responseIf the job action was requested by a stored procedure,correct the invalid job identifier on the SQL Callstatement.

Severity12 (severe)

DSNA635I csect-name AN INTERNAL ERROROCCURRED. additional-info

ExplanationAn error has occurred, as indicated by additionalinformation in the message:


additional-infoA string that provides additional details about thereason for the message.


User responseWhen the value of additional-info refers to the SMSINTERFACE, see the information about SMS reasoncodes to diagnose the problem. Otherwise, contactIBM Software Support.


Related referenceStorage Management Subsystem ReasonCodes(z/OS DFSMSdfp Diagnosis)

DSNA636I csect-name DB2 THREAD WASCANCELED

ExplanationThe thread running the stored procedure wascancelled.


User responseIf necessary, issue the SQL CALL statement again.

Severity12 (severe)

DSNA637I csect-name I/O ERROR ON DATASET

ExplanationAn I/O error occurred while processing a data set orlibrary member.


User responseLook at the messages in the console log for moreinformation. If necessary, report the problem to IBMSupport.

Severity12 (severe)

DSNA638I csect-name THE SEQUENCENUMBER seq IN ROW rownum OFTABLE table-name IS OUT OFSEQUENCE

ExplanationThe sequence number of the rows in the indicatedtable is not in ascending sequence, or the rowsequence number does not start with 1.


User responseCorrect the sequence number of the rows in theindicated table.

Severity12 (severe)

DSNA639I csect-name THE NUMBER OFROWS table-size IN THE INPUTTABLE table-name AND THENUMBER OF OBJECTS objnumSPECIFIED IN THE PARAMETERparm-name DO NOT MATCH

ExplanationThe number of rows in the indicated table did notmatch the number of objects specified in the namedparameter.


User responseCorrect the number of objects specified in theindicated parameter, or repopulate the named tablewith the correct number of rows.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idar100/smsrr.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idar100/smsrr.htm

Severity12 (severe)

DSNA640I csect-name SHUTDOWNDURATION xxxx REACHED,SHUTDOWN INITIATED

ExplanationWhen the overall execution time reached the indicatedshutdown duration, shutdown was initiated. Whenshutdown is initiated, current utility executions run tocompletion but no new utility will be started.

System actionCurrent utility executions are allowed to run tocompletion, but no new utility will be started.

User responseDetermine which objects have not been processed dueto the shutdown. CallSYSPROC.ADMIN_UTL_SCHEDULE again to processthe unprocessed objects. If necessary, increase theSHUTDOWN_DURATION input parameter on the SQLCALL statement.

Severity4 (warning)

DSNA642I DSNADMCS CALL TO nameINTERFACE FAILED, ATTCHMVSRC=return-code

ExplanationAn error occurred when attaching a Db2 BIND service,DSNESM71, to execute the indicated DSNsubcommand.

nameThe DSN subcommand. Possible values are BIND,REBIND, or FREE.

return-codeThe return code from ATTCHMVS. If return-code is99, a failure occurred when the Db2 BIND serviceissued RRS IDENTIFY, SIGNON, or CREATETHREAD.

System actionThe stored procedure terminates.

System programmer responseFor more information about the ATTCHMVS returncode, see the information about host commandenvironments.


Related referenceHost command environments for linking to andattaching programs (TSO/E REXX Reference)Host commands and host commandenvironments (TSO/E REXX Reference)

DSNA643I csect-name INVALIDCREDENTIALS, ERRNO=errno

ExplanationThe stored procedure is unable to log in because theUSERID or PASSWORD parameter in the SQL CALLstatement is invalid.



Programmer responseSpecify valid credentials in the SQL CALL statement. Ifthe problem persists, ask your security administratorto check the security configuration for the specifieduser.

Severity12 (severe)

DSNA644I THE STORED PROCEDUREprocedure-name CAN ONLY BEEXECUTED IN mode MODE.

ExplanationA stored procedure has been called in a Db2 mode thatis not allowed.

procedure-nameThe name of the stored procedure.

modeThe mode that is required for this storedprocedure.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/lnkatt.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/lnkatt.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/addrtso.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/addrtso.htm

System actionExecution of the stored procedure stops.

User responseChange Db2 to the mode that is identified by mode inthe message and run the stored procedure again.


DSNA645I csect-name THE PARAMETERMAX_INVOCATIONS IS NOT 1ALTHOUGH NO SCHEDULE ISDEFINED

ExplanationThis input parameter must be set to 1 whenparameters INTERVAL, POINT_IN_TIME andTRIGGER_TASK_ID are null.



Programmer responseSpecify 1 for MAX_INVOCATIONS in the SQL CALLstatement.

Severity12 (severe)

DSNA646I csect-name THE PARAMETERparm-name HAS AN INVALIDFORMAT, POS = xx

ExplanationThe specified parameter in the message has an invalidformat. The error was detected at position xx in theparameter value.



Programmer responseCorrect the value for the specified input parameter inthe SQL CALL statement.

Severity12 (severe)

DSNA648I THE ACTION action-name INALERT alert-id IS NOTSUPPORTED.

ExplanationThe stored procedure ADMIN_UTL_EXECUTE did notrecognize the action to be taken to process the alert.

action-nameThe action that the stored procedure could notrecognize.

alert-idThe alert identifier from the catalog tableSYSIBM.SYSAUTOALERTS.

System actionThe stored procedure continues to execute but thealert cannot be processed. The alert is ignored.

User responseVerify that the action is valid and the latest version ofthe stored procedure ADMIN_UTL_EXECUTE isinstalled.

Severity4 (warning)

Related referenceADMIN_UTL_EXECUTE stored procedure (Db2SQL)

DSNA649I ALERTS COULD NOT BE RESOLVEDBY PROCEDURE. REASON reason-code.

ExplanationThe stored procedure ADMIN_UTL_EXECUTE couldnot resolve any alerts.

reason-codeThe reason for the message or SQL code, indicatedby one of the following values:1

ADMIN_UTL_EXECUTE was not executedwithin a maintenance time window.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_adminutlexecute.html


2ADMIN_UTL_EXECUTE did not have enoughtime in the maintenance time window toresolve alerts.

System actionThe stored procedure continues to execute, but thealerts cannot be processed. Alerts are ignored.

User responseCorrect the condition that is indicated by the reason-code value.

Severity4 (warning)


DSNA650I csect-name CANNOT CONNECT TOADMIN SCHEDULER scheduler-name

ExplanationThe stored procedure or user-defined function cannotconnect to the specified administrative task scheduler.Either the name of the administrative task scheduler isincorrect or the administrative task scheduler iscurrently unavailable.


scheduler-nameThe name of the administrative task scheduler.


System programmer responseVerify the name of the administrative task schedulerand change the ADMTPROC subsystem parameter, ifnecessary. Verify that the specified administrative taskscheduler is up and running before calling this storedprocedure again.


Related referenceADMIN SCHEDULER field (ADMTPROCsubsystem parameter) (Db2 Installation andMigration)

DSNA651I csect-name DB2 db2-ssid IS NOTALLOWED TO CONNECT TO ADMINSCHEDULER scheduler-name

ExplanationThe specified administrative task scheduler does notaccept requests from the specified Db2 subsystem.


db2-ssidThe Db2 subsystem identifier. The administrativetask scheduler parameter DB2SSID must be set tothis value in order to accept requests from this Db2subsystem.



System programmer responseVerify the name of the administrative task schedulerand change the ADMTPROC subsystem parameter, ifnecessary. Verify that the specified administrative taskscheduler is set up to accept requests from thespecified Db2 subsystem.


Related referenceADMIN SCHEDULER field (ADMTPROCsubsystem parameter) (Db2 Installation andMigration)

DSNA652I csect-name THE USER user-nameIS NOT ALLOWED TO ACCESSTASK task-id

ExplanationThe specified user, which is the value to which thespecial register CURRENT SQLID is set, is not allowedto update or delete the specified task. This user didnot create the task and does not have SYSOPR,SYSCTRL, or SYSADM authority.




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_admtproc.html






The csect-name in the message identifies the CSECTthat issues the message.


Programmer responseEnsure that the Db2 special register (CURRENT SQLID)is set to the same user that added this task, or to auser that has SYSOPR, SYSCTRL, or SYSADM authority,before calling this stored procedure again.

Severity12 (severe)

DSNA653I csect-name CANNOT FIND ZPARMzparm-name

ExplanationThe specified subsystem parameter (ZPARM) value isnot defined.


zparm-nameThe name of the subsystem parameter that is notdefined.

The csect-name in the message identifies the CSECTthat issues the message.


System programmer responseDefine the specified subsystem parameter value.

If the subsystem parameter value is defined and thefailing procedure is an administrative schedulerprocedure, ensure that the user ID that runs the job isgranted the MONITOR1 and MONITOR2 privileges.

Severity12 (severe)

Related conceptsSubsystem parameters (Introduction to Db2 forz/OS)Architecture of the administrative taskscheduler (Db2 Administration Guide)

Related referenceDirectory of subsystem parameters, panelfields, and application default values (Db2Installation and Migration)System privileges (RACF Access Control ModuleGuide)

DSNA654I csect-name THE TASK task-nameDOES NOT EXIST

ExplanationThe specified task cannot be updated or removedbecause it does not exist in the administrative taskscheduler task list.


task-nameThe unique name of the scheduled administrativetask.


Programmer responseVerify the task ID. Correct the task ID, if necessary,and resubmit the request.


DSNA655I csect-name THE TASK task-nameHAS AN EXECUTION STATUS THATIS NOT COMPATIBLE WITH THEREQUESTED ACTION.

ExplanationThe specified task cannot be removed because it iscurrently executing, or it cannot be cancelled becauseit is not executing.


task-nameThe unique name of the task to be removed orcancelled.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_zparm.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_zparm.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_taskschedulerarchitecture.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_zparmdir.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/racf/src/tpc/db2z_systemprivs.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/racf/src/tpc/db2z_systemprivs.html

Programmer responseWait for the completion of this task before trying toremove it. Use the DSNADM.ADMIN_TASK_STATUSuser-defined function to check the execution status ofthe task.

Severity12 (severe)

DSNA656I csect-name THE ADMINSCHEDULER scheduler-name TASKLIST IS FULL

ExplanationThe task list for the specified administrative taskscheduler has reached its maximum size. No tasks canbe added until other tasks are removed from the tasklist.




Programmer responseDelete one or more tasks that have already beenexecuted and whose status is no longer required.


Related tasksRemoving a scheduled task (Db2 AdministrationGuide)

DSNA657I csect-name THE ADMINSCHEDULER scheduler-nameCANNOT ACCESS ITS TASK LISTS

ExplanationThe specified administrative task scheduler cannotaccess any of its task lists to make the requestedchanges. Tasks cannot be added, removed, orupdated.



System actionThe stored procedure and the administrative taskscheduler both terminate.

System programmer responseCheck the operator console messages for othermessages about the administrative task scheduler, andtake the appropriate action or actions.

At least one of the redundant administrative taskscheduler task lists must be available to start theadministrative task scheduler.


Related conceptsTask lists of the administrative task scheduler(Db2 Administration Guide)

DSNA658I csect-name THE parameter-namePARAMETER WAS MODIFIEDchange-type IN MODULE module-name BY USER authorization-name. THE OLD SETTING WAS old-setting. THE NEW SETTING ISnew-setting.

ExplanationA user modified the value of the specified Db2subsystem parameter by using theSYSPROC.ADMIN_UPDATE_SYSPARM storedprocedure. This message is an informational messagethat is issued once for every parameter that wasmodified by this stored procedure.


parameter-nameThe subsystem parameter for which the value wasmodified.

change-typeThe type of change, which can be one of thefollowing values:ONLINE

SYSPROC.ADMIN_UPDATE_SYSPARM used theSET SYSPARM command to load modulemodule-name and change the value of thesubsystem parameter immediately.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_removescheduledtask.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_removescheduledtask.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_schedulertasklists.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_schedulertasklists.html

OFFLINEThe new value of the subsystem parameterdoes not become effective until the next timethat Db2 is started with module module-name.

module-nameThe name of the subsystem parameter loadmodule.

authorization-nameThe authorization ID of the user who requested thechange.

old-settingThe value of the subsystem parameter before thechange was requested.

new-settingThe new value of the subsystem parameter.

System actionProcessing continues.

User responseNo action is required.

Related referenceADMIN_UPDATE_SYSPARM stored procedure(Db2 SQL)-SET SYSPARM (Db2) (Db2 Commands)

DSNA659I csect-name THE TASK task-nameTRIGGERS DEPENDENT TASKS

ExplanationThe execution of the specified task triggers theexecution of one or more tasks defined in theadministrative task scheduler task list. This taskcannot be removed until the dependencies have beenremoved.




Programmer responseRemove the dependent tasks.


DSNA660I csect-name AN INTERNAL ERRORHAS OCCURRED

ExplanationThe administrative task scheduler could not accessinternal resource that should be available.



System programmer responseGather the administrative task scheduler trace, andcontact IBM support.


DSNA661I csect-name THE MACRO macro-name FAILED WITH RETURNCODE=return-code

ExplanationA Db2 stored procedure attempted to use a z/OSmacro to identify attributes of a data set, and themacro failed.


macro-nameThe name of the z/OS macro.

return-codeA numeric value that indicates the reason for thefailure. This return code is issued by z/OS.


Programmer responseReview the return codes for the macro that is identifiedby the macro-name value and take the indicatedaction.

Related referenceDFSMS Macro Instructions for Data Sets


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_adminupdatesysparm.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_setsysparm.html

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/toc.htm

MVS Programming: Authorized AssemblerServices Reference SET-WTORelated informationDFSMSdfp Advanced Services

DSNA662I csect-name CATALOGMANAGEMENT HAS DETECTED ANERROR FOR entry-name. RETURNCODE=return-code, REASONCODE=reason-code

ExplanationA catalog error occurred when a Db2 stored procedureattempted to use the Catalog Search Interface toobtain information about data sets.


entry-nameThe entry name returned by the Catalog SearchInterface.

return-codeA numeric value that indicates the reason for thefailure. This return code is issued by catalogmanagement.

reason-codeA numeric value that indicates the reason for thefailure. This reason code is issued by catalogmanagement.


Programmer responseUse the information provided for the return and reasoncodes for message IDC3009I to correct the catalogerror.

Related referenceMessage IDC3009I (MVS System Messages)

DSNA663I csect-name THE ATTRIBUTES OFdataset-count DATA SETS HAVENOT BEEN SUCCESSFULLYRETRIEVED.

ExplanationThe Db2 stored procedure ADMIN_DS_LIST could notretrieve all attributes of one or more data sets.


dataset-countThe number of rows in the result set where theERRMSG column is not blank. If a data set spansmore than one volume, and ADMIN_DS_LIST couldnot retrieve all the attributes of a volume wherethis data set resides, this volume counts as onerow in the count.


Programmer responseScan the ERRMSG column of the result set to identifythe data sets whose attributes have not all beensuccessfully retrieved. Use the information provided inthe ERRMSG column to correct the data set error.

DSNA664I csect-name THE VOLUME SPACESTATISTICS OFobject-countOBJECTS HAVE NOT BEENSUCCESSFULLY RETRIEVED.

ExplanationThe ADMIN_INFO_SMS stored procedure was unableto retrieve the volume space statistics for one or moreobjects.csect-name

The name of the control section that issued themessage.

object-countThe number of rows in the result set that containnon-blank values in the ERRMSG column.


Programmer responseScan the ERRMSG column of the result set to identifythe objects whose volume space statistics have notbeen successfully retrieved. Use the informationprovided in the ERRMSG column to correct the error.

Related referenceADMIN_INFO_SMS stored procedure (Db2 SQL)

DSNA665I csect-name THE ALERT skipped-alert CANNOT BE EXECUTED.REASON=reason-text




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idas300/toc.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieam600/bb3009i.htm

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_admininfosms.html

ExplanationThe stored procedure ADMIN_UTL_EXECUTE did notexecute the indicated alert because it executed adifferent alert instead.


skipped-alert and alternate-alertUnique alert IDs. These values represent theprimary key (ALERT_ID column) of a row in theSYSIBM.SYSAUTOALERTS table.

This message always includes two alert IDs. Thefirst alert ID in the message (skipped-alert) is notexecuted. The second alert ID in the message(alternate-alert, which is part of the reason-text), isexecuted instead of the skipped alert. The twoalert IDs refer to the same object, such as a tablespace.

reason-textA brief explanation of why the skipped alert wasnot executed, including the ID of the alert that wasexecuted in its place.ACTION OVERRULED BY ALERT alternate-alert

The action to solve the skipped alert isoverruled by the action to solve the indicatedone.

ALREADY EXECUTING SIMILAR ALERTalternate-alert

The action to solve the skipped alert is thesame as the action to solve the indicated one,and the action is currently executing.

System actionThe skipped alert (skipped-alert) is not executed and ismarked as completed. The alternate alert (alternate-alert) is executed instead.


Severity0 (informational)


DSNA666I csect-name A REQUIRED ACTIONWAS NOT COMPLETED AFTER THESUBSYSTEM PARAMETERS WEREMODIFIED. ACTION-TYPE= action-

type. REASON CODE=reason-code.additional-info

ExplanationA user modified the value of at least one Db2subsystem parameter by using theSYSPROC.ADMIN_UPDATE_SYSPARM storedprocedure. However, Db2 did not complete a requiredor requested action after the subsystem parametervalues were changed.

Message DSNA666I is returned in the result table ofthe SYSPROC.ADMIN_UPDATE_SYSPARM storedprocedure.


action-typeA numeric value that identifies the action thatfailed. action-type can be one of the followingvalues:01

The SET SYSPARM command with the LOADoption was not invoked.

02The message DSNA658I was not displayed onthe JES SYSLOG.

reason-codeA numeric value that indicates the reason for thefailure. reason-code can be one of the followingvalues:01

The meaning depends on the action-type valueas follows:

• If the action-type is 01, at least one modifiedsubsystem parameter cannot be changedonline.

• If the action-type is 02, the stored procedureencountered an error while displaying aDSNA658I message on the JES SYSLOG.

02Synchronous processing of the SET SYSPARMcommand is not supported.

additional-infoAdditional descriptive text that explains the reasonthat the specified action failed.

Although additional-info is part of messageDSNA666I, it is not returned in the same result setrow. additional-info is returned in a separate rowafter DSNA666I.





User responseDepending on the value of action-type and reason-code take one of the following actions:

action-typevalue

reason-codevalue

Corrective action

01 01 In the input tableSYSIBM.SYSPARM_SETTINGS,specify only those subsystemparameters that can be changedonline.

01 02 Ensure that APAR PM40501 isinstalled.

02 01 Check for the return code frommodule DSNADMCC in theadditional-info field and reportthe problem to IBM SoftwareSupport.

Related referenceADMIN_UPDATE_SYSPARM stored procedure(Db2 SQL)-SET SYSPARM (Db2) (Db2 Commands)Related informationDSNA658Icsect-name THE parameter-name PARAMETERWAS MODIFIED change-type IN MODULEmodule-name BY USER authorization-name.THE OLD SETTING WAS old-setting. THE NEWSETTING IS new-setting.

DSNA667I csect-name AN ERROR WASENCOUNTERED WHEN ADDING ORDELETING THE environment-nameHOST COMMAND ENVIRONMENTUSING function-name.ACTION=action-type. RC=return-code.

ExplanationA Db2 stored procedure attempted to add or delete ahost command environment, but the host commandenvironment add or delete failed.


environment-nameThe name of the host command environment:DSNREXX or SDSF.

function-nameThe function that was invoked: RXSUBCOM orISFCALLS.

action-typeThe action that was specified: ADD or DELETE.

return-codeA numeric value that provides information aboutthe failure. This return code is issued by the hostcommand environment.

If function-name is RXSUBCOM and return-code is40, RXSUBCOM found an error in the parameter listpassed to it, such as too many or too fewparameters.


Programmer responseReview the return code information for the hostcommand environment and take the indicated action.

Related referenceReturn codes for ISFEXEC (z/OS SDSFOperation and Customization)Return codes for IRXSUBCM (TSO/E REXXReference)

DSNA668I csect-name AN ERROR WASENCOUNTERED WHEN INVOKINGTHE HOST ENVIRONMENTCOMMAND host-command WITHOPERAND operand-name.RC=return-code.

ExplanationA Db2 stored procedure invoked a host environmentcommand and the command failed.


host-commandThe name of the host environment command:ISFEXEC or ISFLOG.

operand-nameThe name of the operand that was specified for thehost command.





http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.isfa500/hcrc.htm


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/rsubccd.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/rsubccd.htm

return-codeA numeric value that provides information aboutthe failure. This return code is issued by the hostcommand environment.

If return-code is 12 and message DSNA668I isfollowed by the following SDSF messages, the storedprocedure must be executed on a system that hasz/OS V1R12 or later installed.

ISF302E string was seen in command position1 where one of the following was expected: END-OF-STMT, ISFACT, ISFEXEC, ISFGET. ISF767I Request completed

System actionProcessing terminates. This message might befollowed by one or more messages from the hostenvironment command.

Programmer responseCheck for additional messages from the hostenvironment command. Review the return codeinformation for the host environment command andtake the indicated action.

Related referenceReturn codes for ISFEXEC (z/OS SDSFOperation and Customization)Return codes for ISFLOG (z/OS SDSF Operationand Customization)

DSNA669I csect-name THE SUBSYSTEMPARAMETERS WERE NOTMODIFIED. REASONCODE=reason-code. additional-info

ExplanationA user requested a change to the value of at least oneDb2 subsystem parameter by using theSYSPROC.ADMIN_UPDATE_SYSPARM storedprocedure. However, the subsystem parameters werenot modified for the indicated reason.

Message DSNA669I is returned in the result table ofthe SYSPROC.ADMIN_UPDATE_SYSPARM storedprocedure, unless the reason-code value is 01, 04, 05,06, or 07. In these special cases, DSNA669I isdisplayed in the WLM job log.


reason-codeA numeric value that indicates the reason for thefailure. reason-code can be one of the followingvalues:

01A REXX programming violation occurred.

02The created global temporary tableSYSIBM.SYSPARM_SETTINGS does not exist.

03The user does not have the authority to use thecreated global temporary tableSYSIBM.SYSPARM_SETTINGS.

04The created global temporary tableSYSIBM.UPDSYSPARM_MSG does not exist.

05The user does not have authority to use thecreated global temporary tableSYSIBM.UPDSYSPARM_MSG.

06The DSNREXX package was not found.

07Db2 cannot access a DSNREXX environment.Db2 REXX Language Support is not available.

08All libraries in the WLM STEPLIB concatenationare APF-authorized.

09An error occurred when validating an inputparameter for the stored procedure.

10The WLM startup procedure is missing theZPMDFLTS DD statement.

11A data set that is required by the storedprocedure is not available for use.

12A validation error occurred for input tableSYSIBM.SYSPARM_SETTINGS for one of thefollowing reasons:

• The table is empty.• The table has a duplicate ROWNUM value.• The table has a negative ROWNUM value.• A macro name is invalid.• A parameter is invalid.

13An SQL error occurred when retrieving newsubsystem parameter values from the inputtable SYSIBM.SYSPARM_SETTINGS.

14The specified source_library parameter for theADMIN_UPDATE_SYSPARM stored procedureis not a partitioned data set (PDS) or apartitioned data set extended (PDSE).




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.isfa500/logrc.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.isfa500/logrc.htm

15The record format (RECFM) of the specifiedsource_library parameter for theADMIN_UPDATE_SYSPARM stored procedureis not F or FB.

16The record length (LRECL) of the specifiedsource_library parameter for theADMIN_UPDATE_SYSPARM stored procedureis not 80.

17The ZPMDFLTS DD statement in the WLMstartup procedure points to a data set thatcontains a SRCLIB_NAME library data set. ThatSRCLIB_NAME data set is not a partitioneddata set (PDS) or a partitioned data setextended (PDSE).

18The ZPMDFLTS DD statement in the WLMstartup procedure points to a data set thatcontains a SRCLIB_NAME library data set. Therecord format (RECFM) of that SRCLIB_NAMEdata set is not F or FB.

19The ZPMDFLTS DD statement in the WLMstartup procedure points to a data set thatcontains a SRCLIB_NAME library data set. Therecord length (LRECL) of that SRCLIB_NAMEdata set is not 80.

20The backup of the member that the storedprocedure is to replace did not completesuccessfully. The member was to be replacedwith the new JCL to assemble and link-edit thenew subsystem parameters load module. Thefailure occurred for one of the followingreasons:

• A backup already exists.• An I/O error occurred.

21One of the following errors occurred whenretrieving the current values of the subsystemparameters:

• The SYSPROC.ADMIN_INFO_SYSPARMstored procedure did not completesuccessfully. Either the return code wasgreater than 0 or the SQL code was not +466,as expected.

• An SQL error occurred when processing theresult set from theSYSPROC.ADMIN_INFO_SYSPARM storedprocedure.

22The required program ASMA90 was not found.

23The required program HEWL (which executesthe linkage editor) was not found.

24The process of assembling the subsystemparameter macros did not completesuccessfully. The return code was greater than0.

25The backup of the subsystem parameters loadmodule that is being replaced did not completesuccessfully for one of the following reasons:

• The backup already exists.• A SYSDSN error occurred for a backup

member.• IEBCOPY failed to make a backup copy.

26The process of link-editing the subsystemparameters load module did not completesuccessfully. The return code was greater than4.

27The SET SYSPARM command with the LOADoption did not complete successfully for one ofthe following reasons:

• The SYSPROC.ADMIN_COMMAND_DB2stored procedure did not completesuccessfully. Either an IFI error occurred, thereturn code was greater than 0, or the SQLcode was not +466, as expected.

• The SET SYSPARM command returnedmessages that indicate that the commandwas not successful.

28The result of the SET SYSPARM command withthe LOAD option is unknown. An SQL erroroccurred when processing the result set of theADMIN_COMMAND_DB2 stored procedure.

32An I/O error occurred when accessingassembler and link-edit files.

33The JCL to assemble and link-edit the newsubsystem parameters load module was notsaved for one of the following reasons:

• A data set allocation error occurred.• A data set I/O error occurred.


34The SYSPROC.ADMIN_UPDATE_SYSPARMstored procedure could not retrieve thesubsystem name of the connected Db2subsystem.

35The SYSPROC.ADMIN_UPDATE_SYSPARMstored procedure could not retrieve thesubsystem name and command prefix of theDb2 subsystem whose subsystem parametersare to be modified. This situation occurred forone of the following reasons:

• The SYSPROC.ADMIN_COMMAND_DB2stored procedure did not completesuccessfully. Either an IFI error occurred, thereturn code was greater than 0, or the SQLcode was not +466, as expected.

• An SQL error occurred when processing theresult set from the ADMIN_COMMAND_DB2stored procedure.

• The version of Db2 is not supported.

additional-infoAdditional descriptive text or another messagethat explains the reason that the specified actionfailed.

Although additional-info is part of messageDSNA669I, it is not returned in the same result setrow. additional-info is returned in a separate rowafter DSNA669I. The exception is if the reason-code value is 01, 04, 05, 06, or 07. In these specialcases, DSNA669I and the additional text aredisplayed in the WLM job log.

System actionThe SYSPROC.ADMIN_UPDATE_SYSPARM storedprocedure terminates, unless the error is encounteredduring cleanup or restore processing.

User responseCheck the additional-info field for a more detailedexplanation of the error and take the appropriateaction.

• If a DSN message is specified, see the informationfor the specific Db2 for z/OS message.

• If an EXECIO error was encountered, see theinformation about EXECIO for a description of thereturn code.

• If an allocation error was encountered, see theinformation about the ALLOCATE TSO/E commandfor a description of the ALLOCATE return code. Also,check the ALLOCATE error message that wasreturned by the stored procedure. The ALLOCATE

error message is in the result set row after the rowwhere the ALLOCATE return code is specified.

• If an assembly, link-edit, or IEBCOPY error wasencountered, check the corresponding listing that isreturned by the stored procedure.

Related referenceADMIN_UPDATE_SYSPARM stored procedure(Db2 SQL)EXECIO (TSO/E REXX Reference)ALLOCATE command (TSO/E CommandReference)

DSNA670I csect-name THE ADMINSCHEDULER scheduler-name ISSTOPPING

ExplanationThe specified administrative task scheduler isstopping.



System actionThe administrative task scheduler stops.



DSNA671I csect-name THE ADMINSCHEDULER scheduler-name ISSTARTING

ExplanationThe specified administrative task scheduler is starting.



System actionThe administrative task scheduler starts.




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikja300/dup0037.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikjc500/dup0009.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ikjc500/dup0009.htm



DSNA672I csect-name action-descriptionscheduler-name NORMALCOMPLETION

ExplanationThe indicated action completed successfully for thespecified administrative task scheduler.


action-descriptionThe action that has completed. Possible actionsinclude:

• START COMMAND FOR ADMIN SCHEDULER• STOP COMMAND FOR ADMIN SCHEDULER• MODIFY COMMAND FOR ADMIN SCHEDULER


System actionThe administrative task scheduler executed thespecified action.



DSNA673I csect-name action-descriptionscheduler-name ABNORMALTERMINATION

ExplanationThe described action was terminated because of anerror in the specified administrative task scheduler.


action-descriptionThe action that did not complete. Possible actionsinclude:

• START COMMAND FOR ADMIN SCHEDULER• STOP COMMAND FOR ADMIN SCHEDULER• MODIFY COMMAND FOR ADMIN SCHEDULER• EXECUTION LOOP OF ADMIN SCHEDULER


System actionThe administrative task scheduler terminates.

Programmer responseInvestigate other error messages that were displayedon the operator's console prior to this message.


DSNA674I csect-name THE ADMINSCHEDULER scheduler-name ISALREADY ACTIVE

ExplanationThe administrative task scheduler that is starting uphas detected another address space with the samename that is already running on the system. Only oneinstance of the administrative task scheduler isallowed to run.



System actionThe administrative task scheduler that was alreadyrunning remains active. The one that was startingterminates.



DSNA675I csect-name module-name COULDNOT RUN BECAUSE IT WAS NOTINVOKED FROM AN APF-AUTHORIZED LIBRARY


ExplanationThe load module could not run.


module-nameThe name of the load module.

Either of the following conditions can cause this error:

• The load module that is identified by module-namewas not invoked from an APF-authorized library.

• One or more libraries in the STEPLIB or JOBLIBconcatenation in the job that invokes the loadmodule that is identified by module-name is notAPF-authorized.

System actionThe administrative task scheduler, stored procedure,or batch program is not started.

System programmer responseEnsure that all libraries in the STEPLIB and JOBLIBconcatenation for the job that invokes module-nameare APF-authorized.

User responseNotify the system programmer.


DSNA676I csect-name SEVERE ERRORENCOUNTERED WHILE STARTINGOR STOPPING ADMIN SCHEDULERscheduler-name

ExplanationA severe error has been detected in the specifiedadministrative task scheduler.



System actionThe administrative task scheduler terminates.

Programmer responseGather the administrative task scheduler trace, andcontact IBM support.


DSNA677I csect-name THE application-typeprocedure-name CAN ONLYCREATE threads-created OFthreads-requested THREADS

ExplanationThere are not enough resources available to create allthe requested threads.


application-type and procedure-nameThe type and name of the application.ADMIN SCHEDULER

The procedure is the administrative taskscheduler. The name that is provided is thename of a scheduled task.

STORED PROCEDUREThe procedure is a stored procedure. The namethat is provided is the name of the storedprocedure.

threads-createdThe number of threads that were created.

threads-requestedThe number of threads that were requested.

System actionThe administrative task scheduler or stored procedureterminates.

System programmer responseTake the action indicated by the value of application-type:

ADMIN SCHEDULEREither increase system resources to allow theadministrative task scheduler to create the numberof threads needed, or lower the maximum numberof threads that the administrative task scheduler isallowed to use. The parameter MAXTHD controlsthe maximum number of threads that theadministrative task scheduler is allowed to use.


STORED PROCEDUREEither reduce the number of parallel threads, orincrease the value of the CTHREAD subsystemparameter to allow the stored procedure to createthe number of threads indicated by the value ofthreads-requested.


Related conceptsMulti-threading in the administrative taskscheduler (Db2 Administration Guide)Related tasksInstallation step 22: Set up the administrativetask scheduler (Db2 Installation and Migration)Related referenceMAX USERS field (CTHREAD subsystemparameter) (Db2 Installation and Migration)

DSNA678I csect-name THE NUMBER OFTASKS TO BE CONCURRENTLYEXECUTED BY THE ADMINSCHEDULER scheduler-nameEXCEEDS max-threads

ExplanationThe current number of tasks to be executedconcurrently exceeds the maximum number of threadsthat is allowed by the specified administrative taskscheduler.



max-threadsThe number of threads that were created.

System actionThe administrative task scheduler continues running,but some scheduled tasks cannot be executed.

Programmer responseChange the execution schedule of some tasks, ifpossible.


Related conceptsMulti-threading in the administrative taskscheduler (Db2 Administration Guide)Related tasksInteracting with the administrative taskscheduler (Db2 Administration Guide)

DSNA679I csect-name THE ADMINSCHEDULER scheduler-nameCANNOT ACCESS TASK LIST task-list, REASON = reason-indicator

ExplanationThe specified administrative task scheduler cannotaccess the task list.



task-listThe task list, which can be either a VSAM data setthat contains the task list or the Db2 tableSYSIBM.ADMIN_TASKS that contains theredundant task list.

reason-indicatorAn indicator of the reason for the failure, which canbe a VSAM access error, an SQL error code, or aDb2 error code.

System actionThe administrative task scheduler continues runningwith access to the other task list only.

System programmer responseVerify the name of the VSAM data set and modify theadministrative task scheduler started task procedure,if necessary. Stop and restart the administrative taskscheduler with this new configuration.

Verify that Db2 is up and running and that thescheduler can connect to it and has access to the Db2task list.

According to the reason specified, make sure thefollowing conditions are met.

• The VSAM data set exists.• The VSAM data is allocated.• The VSAM data can be accessed from this system.• The user who started the administrative task

scheduler is allowed to access it for read and write.• The Db2 system is up and running.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_multithreadingtaskscheduler.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_setupadminsched.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_cthread.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_cthread.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_usingtaskscheduler.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_usingtaskscheduler.html

• The administrative task scheduler packages arecorrectly bound in Db2.

• The Db2 table SYSIBM.ADMIN_TASKS containing thetask list exists.

• The user who started the administrative taskscheduler is allowed to access it for read and write.


DSNA681I csect-name THE ADMINSCHEDULER scheduler-name TASKLIST vsam-list AND table-list AREINCONSISTENT

ExplanationThe specified administrative task scheduler hasdetected that the redundant task lists do not match.



vsam-listThe task list that is stored as a VSAM data set.

table-listThe task list that is stored in a Db2 table.

System actionThe administrative task scheduler tries recovering theolder task list from the newer task list.

Programmer responseLook for additional messages that indicate the result ofthe recovery process.


Related conceptsArchitecture of the administrative taskscheduler (Db2 Administration Guide)

DSNA682I csect-name THE ADMINSCHEDULER scheduler-name TASKLIST task-list IS SUCCESSFULLYRECOVERED

ExplanationThe specified administrative task scheduler hassuccessfully recovered a corrupted or outdated tasklist from the redundant task list.



task-listThe task list that has been recovered.

System actionBoth task lists are in a consistent state.



DSNA683I csect-name THE ADMINSCHEDULER scheduler-name TASKLIST task-list CANNOT BERECOVERED

ExplanationThe specified administrative task scheduler could notrecover a corrupted or outdated task list from theredundant task list.



task-listThe task list that could not be recovered.

System actionThe administrative task scheduler continues runningwith access to only one task list.

Programmer responseGather the administrative task scheduler trace, andcontact IBM support.





DSNA684I csect-name DFLTUID CANNOT BETHE USER user-name THATSTARTS THE ADMIN SCHEDULERscheduler-name

ExplanationThe specified administrative task scheduler startedtask parameter (DFLTUID) is set to the specified username. This user is the same user that is associatedwith the started task. For security reasons, thisassignment is not allowed.


user-nameThe user name that was provided to start theadministrative task scheduler. This name isspecified in the DFLTUID parameter.


System actionThe administrative task scheduler does not start.

System programmer responseSpecify another user name in the DFLTUID parameter.The default execution user should have minimalaccess rights on the system, and should have noaccess to administrative task scheduler resources.


Related tasksInstallation step 22: Set up the administrativetask scheduler (Db2 Installation and Migration)Related referenceSecurity guidelines for the administrative taskscheduler (Db2 Administration Guide)

DSNA685I csect-name application-nameaction-type PROCESSING DID NOTCOMPLETE SUCCESSFULLY.OBJECT-TYPE=object-type,OBJECT-NAME=object-name,OBJECT-BACKUP-NAME=object-backup-name. additional-info

ExplanationOne of the following events occurred:

• An object was not restored after the application thatreplaced it failed to complete successfully.

• A new object or a backup object was not deletedafter the application that created it failed tocomplete successfully.

• A backup object was not deleted after thatapplication the created it completed successfully.

Message DSNA685I is returned in the result table ofthe SYSPROC.ADMIN_UPDATE_SYSPARM storedprocedure.


application-nameThe name of the application.

action-typeThe type of action that did not complete. action-type can be one of the following values:CLEANUP

The cleanup processing that occurs whenapplication-name completes, regardless ofwhether the application is successful. Anattempt to delete either object-name or object-backup-name failed.

RESTOREThe restore processing that occurs whenapplication-name does not completesuccessfully and must restore all replacedobjects to their state before the applicationwas run. An attempt to restore an object fromthe object backup failed.

object-typeA numeric value that identifies the type of objectthat was not cleaned up or restored. object-typecan be one of the following values:01

The JCL to assemble and link-edit thesubsystem parameters load module.

02The subsystem parameters load module.

03The active subsystem parameters load modulein storage.

object-nameThe name of the object.

object-backup-nameThe name of the backup object.

additional-infoAdditional text that describes the failure.

Although additional-info is part of messageDSNA685I, it is not returned in the same result set




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_adminschedulersecurity.html


row. additional-info is returned in a separate rowafter DSNA685I.


User responseDepending on the values in the message, take theaction as indicated in the following table:

action-typevalue

object-typevalue

Descriptionof the error

object-namevalue

object-backup-namevalue

Userresponse

CLEANUP 01 Thememberthatcontainsthe newJCL toassembleand link-edit thenewsubsystemparametersloadmodulewas notdeleted.

The nameof thememberwith thenew JCL

NA Delete thememberwith thespecifiedobject name(object-name) fromthe JCLsourcelibrary.

CLEANUP 01 The backupof thememberthat thestoredprocedurereplacedwith thenew JCL toassembleand link-edit thenewsubsystemparametersloadmodulewas notdeleted.

NA Thebackupname ofthememberthat thestoredprocedurereplacedwith thenew JCL

Delete thememberwith thespecifiedbackupobject name(object-backup-name ) fromthe JCLsourcelibrary.

CLEANUP 02 Thememberwith thenewsubsystem

The nameof thememberwith thenew

NA Delete thememberwith thespecifiedobject name

action-typevalue

object-typevalue


object-namevalue


Userresponse

parametersloadmodulewas notdeleted.

subsystemparametersloadmodule

(object-name) fromthesubsystemparametersload modulelibrary.

CLEANUP 02 The backupof thememberthat thestoredprocedurereplacedwith thenewsubsystemparametersloadmodulewas notdeleted.

NA Thebackupname ofthememberthat thestoredprocedurereplacedwith thenewsubsystemparametersloadmodule

Delete thememberwith thespecifiedbackupobject name(object-backup-name ) fromthesubsystemparametersload modulelibrary.

RESTORE 01 Thememberthat thestoredprocedurereplacedwith thenew JCLthatassemblesand link-edits thenewsubsystemparametersloadmodulewas notrestored.

The nameof thememberwith thenew JCL

Thebackupname ofthememberthat thestoredprocedurereplacedwith thenew JCL

Rename thememberwith thespecifiedbackupobject name(object-backup-name ) in theJCL sourcelibrary to thespecifiedobject name(object-name).

RESTORE 02 Thememberthat thestoredprocedurereplacedwith thenewsubsystemparameters

The nameof thememberwith thenewsubsystemparametersloadmodule

Thebackupname ofthememberthat thestoredprocedurereplacedwith the

Rename thememberwith thespecifiedbackupobject name(object-backup-name ) in thesubsystem


action-typevalue

object-typevalue


object-namevalue


Userresponse

loadmodulewas notrestored.

newsubsystemparametersloadmodule

parametersload libraryto thespecifiedobject name(object-name).

RESTORE 03 Thereplacedactivesubsystemparametersloadmodule instorage wasnotrestored.

The nameof thesubsystemparametersloadmodule instoragebefore thestoredprocedureissued theSETSYSPARMcommandwith theLOADoption.

NA From theconsole,issue theSETSYSPARMcommandwith theLOAD(object-name)clause.

Related referenceADMIN_UPDATE_SYSPARM stored procedure(Db2 SQL)-SET SYSPARM (Db2) (Db2 Commands)

DSNA686I csect-name BIND QUERY FORQUERYNO = queryno-valueSUCCESSFUL, BUTSET_PLAN_HINT IS UNABLE TORETRIEVE THE information-type.REASON: reason-text

ExplanationA BIND QUERY command issued by theSET_PLAN_HINT stored procedure has completedsuccessfully. However, the SET_PLAN_HINT storedprocedure cannot retrieve the BIND QUERY messageor the QUERYID value.


queryno-valueThe QUERYNO value that identifies the SQLstatement.

reason-textText the describes why the message output for theBIND QUERY message was not be retrieved.

information-typeA string that indicates the type of information thatwas not retrieved:

• QUERY MESSAGE• QUERYID

System actionThe stored procedure performs terminates normally.



Related referenceSET_PLAN_HINT stored procedure (Db2 SQL)BIND QUERY (DSN) (Db2 Commands)

DSNA687I csect-name ADMIN_INFO_SQLOUTPUT IS INCOMPLETE DUE TOTHE FOLLOWING MISSINGEXPLAIN TABLES: table-list

ExplanationStored procedure SYSPROC.ADMIN_INFO_SQL wasissued to collect EXPLAIN output. One or more of thetables from which ADMIN_INFO_SQL gathers EXPLAINoutput were missing. This might result in insufficientinformation for problem analysis.


table-listA comma-separated list of the missing EXPLAINtables.

System actionProcessing continues. The EXPLAIN output thatADMIN_INFO_SQL collects is incomplete.

User response:Define the missing tables, run EXPLAIN on the query,and call ADMIN_INFO_SQL to collect completeEXPLAIN output. See member DSNTESC in theprefix.SDSNSAMP data set for data definitionstatements for the EXPLAIN tables.





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_setplanhint.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_bindquery.html

Related referenceADMIN_INFO_SQL stored procedure (Db2 SQL)

DSNA690I csect-name THE TASK task-nameWAS RUNNING WHEN THE ADMINSCHEDULER scheduler-nameSTOPPED

ExplanationA task was executing when the specifiedadministrative task scheduler was forced to stop. Thestatus of this task is set to "unknown".




System actionThe administrative task scheduler recovers from ablocked state.

System programmer responseAvoid forcing the administrative task scheduler to stopwhen tasks are currently running. During a normalshutdown of the administrative task scheduler, makesure that no tasks are running.

For a JCL task, make sure that the JCL job, which isindicated in the JOBID in the task execution status,terminates before the next scheduled execution of thistask. If the job is still running from a previousscheduled task, it must be stopped before the taskruns again.


DSNA691I csect-name THE ADMINSCHEDULER scheduler-nameCANNOT GENERATE APASSTICKET FOR TASK task-name, USER user-name

ExplanationThe administrative task scheduler could not generate aPassTicket to switch the security environment. ThisPassTicket is required for the administrative task

scheduler to be able to execute the specified taskunder the authority of the specified user.




user-nameThe user name that must execute the task. Thisuser is not always indicated in the task, and couldbe the default ID, which is set in the DFLTUIDparameter.

System actionThe administrative task scheduler does not executethe specified task.

System programmer responseCheck the security configuration and make sure thatthe administrative task scheduler is allowed to createPassTickets for any user.


Related tasksInstallation step 22: Set up the administrativetask scheduler (Db2 Installation and Migration)Related referenceSecurity guidelines for the administrative taskscheduler (Db2 Administration Guide)

DSNA692I csect-name THE ADMINSCHEDULER scheduler-nameCANNOT LOG IN AS USER user-name RC=return-codeRSN=reason-code

ExplanationThe specified administrative task scheduler cannotswitch the security environment in order to executethe specified task under the authority of the specifieduser.




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_admininfosql.html





user-nameThe user name that was indicated for the task.


return-codeThe return-code returned by the z/OS UNIXSystem Services callable servicepthread_security_np which was used to log in.

reason-codeThe reason-code returned by the z/OS UNIXSystem Services callable servicepthread_security_np which was used to log in.


System programmer responseCheck the security configuration and make sure thatthe specified user exists and can log in.


Related referencethread_security_np(),pthread_security_applid_np() -- Create orDelete Thread-level Security (C/C++ Run-TimeLibrary Reference)Return codes (errnos) z/OS UNIX SystemServices: Messages and CodesReason codes (errnojrs) z/OS UNIX SystemServices: Messages and Codes

DSNA693I csect-name THE ADMINSCHEDULER scheduler-nameCANNOT CONNECT TO DB2 db2-ssid TO EXECUTE TASK task-name

ExplanationThe specified administrative task scheduler wasunable to connect to the specified Db2 subsystemwhen executing the specified stored procedure task.



db2-ssidThe Db2 subsystem identifier.



Programmer responseMake sure that Db2 is up and running when the task isscheduled to run. Make sure that the user that is toexecute the task is allowed to connect to Db2.


DSNA694I csect-name THE ADMINSCHEDULER scheduler-nameCANNOT PROCESS PARAMETERPROCEDURE_INPUT OF TASKtask-name

ExplanationThe parameter PROCEDURE_INPUT for the specifiedtask does not specify an SQL SELECT statement thatreturns one row of data.





Programmer responseRemove the task and add it again.


Related referenceADMIN_TASK_ADD stored procedure (Db2 SQL)ADMIN_TASK_REMOVE stored procedure (Db2SQL)


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxbd00/ptsec.htm




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxa800/errno.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxa800/errno.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxa800/reasoncodes.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxa800/reasoncodes.htm

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_taskadd.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_taskremove.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_taskremove.html

DSNA800I DSNACA00 TCB=x ENTEREDDSNACA00 ACTION=x R1=xCABPTR=x CABFLAG1=xCABFLAG2=x

ExplanationMessages in the DSNA800 series are intended fordiagnosis and are documented in Interpreting tracemessages (Troubleshooting problems in Db2).

Related conceptsInterpreting trace messages (Troubleshootingproblems in Db2)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_trbshootinterpretcallattachtracemessages.html





Chapter 2. DSNB messagesMessage identifiers that begin with DSNB communicate information about the buffer manager.

DSNB200I UPDATE VVDS FAILED. DSNAME =dsn, MMRC=ccccccccCONNECTION-ID=xxxxxxxx,CORRELATION-ID=yyyyyyyyyyyy,LUW-ID=logical-unit-of-work-id=token

ExplanationDb2 was unable to update the data set high-used RBAin the VSAM volume data set (VVDS) when it was readyto close a data set that was used by a RECOVER, LOAD,or REORG utility job. The error was detected by themedia manager catalog update function that issuessystem message IEC161I. The dsn indicates theDSNAME of the data set. MMRC is the return code thatDb2 received from the media manager catalog updateservice. Refer to z/OS DFSMSdfp Diagnosis Referencefor a description of these codes.

The connection ID, correlation ID, and logical-unit-of-work ID (LUW-ID) identify the user or application thatencountered the problem.

An LUW-ID of '*' indicates that the thread does nothave an LUW-ID. If the LUW-ID is not an '*', the value isa logical-unit-of-work-id that is assigned to the threadfollowed by an '=' sign and a token value which can beused in place of logical-unit-of-work-id in any Db2command that accepts logical-unit-of-work-id asinput.

System actionDb2 continues closing this data set. However, theutility job is informed with a 00C2010C 'resourceunavailable' reason code. The utility job is left in afailed state.

Operator responseNotify the system programmer.

System programmer responseTo determine the cause of the error, refer to systemmessage IEC161I in the appropriate MVS publication.Correct the error, and then notify the user to reinvokethe application.

Problem determinationCollect the following diagnostic items:


• IDCAMS LISTCAT output for the ICF (VSAM) catalogthat contains the Db2 subsystem catalog thatdefined the failing index or table.

• IDCAMS LISTCAT output that shows the attributes ofall active log data sets for the Db2 member thatfailed.

DSNB204I OPEN OF DATA SET FAILED.DSNAME = dsn

ExplanationA required data set of a Db2 table or index space couldnot be opened. The error was detected by the mediamanager CONNECT function that issues systemmessage IEC161I. The dsn indicates the DSNAME ofthe data set.

After being issued for a given data set, this message isdisabled for that data set.

System actionBuffer manager functions that detect this conditionterminate.


System programmer responseTo determine the cause of the error, refer to systemmessage IEC161I in the appropriate MVS publication.Correct the error, and reinvoke the application.



• Listing of SYS1.LOGREC data set, obtained byexecuting IFCEREP1.



• VTOC listing of the disk volume on which the failingoperation occurred.

.

DSNB207I DYNAMIC ALLOCATION OF DATASET FAILED. REASON = rrrrDSNAME = dsn

ExplanationA required data set of a Db2 table or index space couldnot be allocated. Reason code rrrr, which is returnedby dynamic allocation, indicates the reason for thefailure. Refer to the appropriate version of the MVSAuthorized Assembler Services Guide (SA22-7608)publication for a description of this reason code. Thedsn indicates the data set's DSNAME.

After being issued for a given data set, this message isdisabled for that data set.

System actionBuffer manager functions that detect this conditionterminate and pass a unique error return code.


System programmer responseCorrect the situation, and then reinvoke theapplication.






.

DSNB209I csect-name-BUFFER MANAGERTABLESPACE/INDEXSPACECLEAN-UP ROUTINE (DSNB1CFC)HAS BEEN SCHEDULED FORDBNAME = database-name,SPACENAME = space-name ,

INSTANCEinstance-number , PSID= X'psid'

ExplanationDb2 detected an abnormal condition for one of thefollowing reasons:

• The associated table space or index space containsmodified pages that cannot be written to DASD for aperiod of time that is longer than expected. Thissituation can be caused by either an unusually longperiod of continuous updates or by an internal logicerror.

• An abnormal termination occurred because ofinconsistent data or an incomplete update to thepage.

Db2 scheduled the table space or index space cleanuproutine (DSNB1CFC) for the associated table space orindex space. DSNB1CFC acquires a drain lock toensure that no updates are in progress. Data isinaccessible to users during the cleanup process.

For recoverable inconsistent pages with unbalancedwrite intents, Db2 initiates the recovery process andreconstructs the pages using the Db2 log. For othermodified pages with unbalanced write intents, thebuffer manager forces the pages to be written back toDASD and then makes the buffer space available forreassignment.


database-nameThe name of the database that is associated withthe action.

space-nameThe name of the table space or index space that isassociated with the action.

instance-numberThe instance number of the table space or indexspace.

psidThe internal identifier for the table space or indexspace. This value is used to associate this messagewith the follow-on message DSNB221I, whichmight be issued.

System actionDb2 is ready to clean up the associated table space orindex space. However, before any cleanup is initiated,Db2 requests a drain on the table space or indexspace. Db2 waits indefinitely for this drain. Therefore,all activities against the table space or index space, orboth, must be quiesced before the cleanup process


can proceed. After the cleanup process completes, thetable space or index space is automatically madeaccessible to users.

User responseIf the cleanup activity does not seem to finish,Db2might still be waiting for a drain on the table space orindex space. Issue a -DISPLAY DATABASE CLAIMERScommand for the table space or index space inquestion to determine whether the cleanup routine isstill waiting for a drain. If it is still waiting, identify theclaimers of the table space or index space. If the jobsare holding claims for a very long duration (forexample, they are waiting for input), you might need tocancel those jobs in order to allow the cleanup processto proceed.

Related reference-DISPLAY DATABASE (Db2) (Db2 Commands)Related informationDSNB221Icsect-name-BUFFER MANAGER TABLESPACE/INDEXSPACE CLEAN-UP PROCESS WAS NOTREQUIRED FOR PSID = X'psid'

DSNB212I csect-name-RECOVER PAGESTARTING DBNAME = database-name, SPACENAME = space-name,INSTANCE = instance-number,PAGE NUMBER = X'page-number'

ExplanationThe buffer manager subcomponent of Db2 discoveredan inconsistent page with unbalanced write intents.Db2 is ready to do online recovery on the page byusing the Db2 log.


database-nameThe name of the database that is associated withthe recovery.

space-nameThe name of the table space or index space that isassociated with the recovery.


page-numberA hexadecimal number that identifies the pagethat is logically inconsistent.

This message is followed by message DSNB215I if therecovery was successful or by message DSNB217I if itwas not successful.



Related informationDSNB215Icsect-name-ONLINE RECOVERY FOR ANINCONSISTENT PAGE HAS BEEN COMPLETEDFOR DBNAME = database-name, SPACENAME =space-name, INSTANCE instance-number, PAGENUMBER = X'page-number'DSNB217Icsect-name-ONLINE RECOVERY FOR ANINCONSISTENT PAGE WAS UNSUCCESSFULFOR DBNAME = database-name , SPACENAME= space-name , INSTANCE= instance-number ,PAGE NUMBER = X'page-number'

DSNB215I csect-name-ONLINE RECOVERYFOR AN INCONSISTENT PAGE HASBEEN COMPLETED FOR DBNAME =database-name, SPACENAME =space-name, INSTANCE instance-number, PAGE NUMBER = X'page-number'

ExplanationThe recovery of an inconsistent page is complete.







Chapter 2. DSNB messages 45

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displaydatabase.html


Related informationDSNB212Icsect-name-RECOVER PAGE STARTINGDBNAME = database-name, SPACENAME =space-name, INSTANCE = instance-number,PAGE NUMBER = X'page-number'

DSNB217I csect-name-ONLINE RECOVERYFOR AN INCONSISTENT PAGEWAS UNSUCCESSFUL FORDBNAME = database-name ,SPACENAME = space-name ,INSTANCE= instance-number ,PAGE NUMBER = X'page-number'

ExplanationThe recovery process for an inconsistent page failed.The page is written to disk as logically inconsistent.This message is issued in response to messageDSNB212I, which was issued to indicate the start ofthe recovery process.






System actionThe page is marked as logically inconsistent and isunavailable until it is repaired. The execution unitdriving this function proceeds normally.

This message is non-scrollable. It remains highlightedon the console until you take the appropriate action.

User responseUse the RECOVER utility with the ERROR RANGEoption to repair the page manually. If the problempersists, contact IBM Support.

Problem determinationMessage DSNI012I might be issued before thismessage to indicate the same failure. If so, a00C90102 abend dump might help determine thecause of this failure. Otherwise, see SYS1.LOGREC forany abend that occurred between the associatedDSNB212I message and this message. Use thetimestamp on the log records to find this abend.

Related conceptsRecovering an error range (Db2 Utilities)Related referenceSyntax and options of the RECOVER controlstatement (Db2 Utilities)Related informationDSNB212Icsect-name-RECOVER PAGE STARTINGDBNAME = database-name, SPACENAME =space-name, INSTANCE = instance-number,PAGE NUMBER = X'page-number'DSNI012IPAGE LOGICALLY BROKEN TYPE resource-typeNAME resource-name MODNAME modnameERQUAL erqual00C90102 (Db2 Codes)

DSNB219I csect-name-BUFFER MANAGERTABLESPACE/INDEXSPACECLEAN-UP PROCESS HAS BEENCOMPLETED FOR DBNAME =database-name, SPACENAME =space-name, INSTANCE instance-number

ExplanationThe buffer manager table space or index spacecleanup process has completed for the associatedtable space or index space. Message DSNB209I, ifpresent, provides additional information about why thebuffer manager scheduled the table space or indexspace cleanup process.


database-nameThe name of the database that is associated withthe action.




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_recovererrorrange.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_recoversyntax.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_recoversyntax.html




Related informationDSNB209Icsect-name-BUFFER MANAGER TABLESPACE/INDEXSPACE CLEAN-UP ROUTINE (DSNB1CFC)HAS BEEN SCHEDULED FOR DBNAME =database-name, SPACENAME = space-name ,INSTANCEinstance-number , PSID = X'psid'

DSNB221I csect-name-BUFFER MANAGERTABLESPACE/INDEXSPACECLEAN-UP PROCESS WAS NOTREQUIRED FOR PSID = X'psid'

ExplanationThis message indicates that the buffer manager (BM)table space or index space cleanup process wasbypassed for the associated table space or indexspace. After quiescing all other activities against thetable space or index space, the buffer managerdiscovered that the table space or index space is nolonger in active mode; that is, it was closed.

The abnormal condition detected earlier was resolvedby buffer manager close page set processing. Refer tothe corresponding message, DSNB209I, using psid asthe matching field, for the reasons the buffer managerschedules the table space or index space cleanupprocess. The psid is the internal identifier for theassociated table space or index space.


DSNB223I csect-name-BUFFER MANAGERTABLESPACE/INDEXSPACECLEANUP PROCESS WASSKIPPED FOR PSID = X'psid'

ExplanationThis message indicates that the table space or indexspace cleanup process was bypassed for theassociated table space or index space. During theprocess of quiescing all other activities against thetable space or index space, an error that is notrecoverable was detected. The error might be causedby any of the following conditions:

• An out-of-storage condition was detected by IRLM.

• The table space or index space was droppedbecause of a backout.

It is assumed that the abnormal condition detectedearlier can later be resolved by the close page setprocessing. Refer to the corresponding messageDSNB209I (use psid as the matching field) for thereasons for scheduling the table space or index spacecleanup process. The psid specifies the internalidentifier for the associated table space or indexspace.


System programmer responseThe associated table space or index space mightcontain inconsistent data. Issue the Db2 STOPTABLESPACE or INDEXSPACE command to allow closepage set processing to perform cleanup for theassociated table space or index space.

DSNB224I csect-name- BUFFER MANAGERI/O ERROR DURING function,DSNAME = data-set-name , PAGENUMBER=X'page-number', MMERROR FLAG=X'aa', CSWSTATUS=X'bbbb', SENSEBYTES=X'cccc', SEEKADDRESS=X'dddddddddddddddd'

ExplanationAn I/O error was encountered by the buffer manager(BM) subcomponent of Db2.


functionThe function that was being performed when theerror occurred. Possible values are READ, WRITE,or FORMAT.

data-set-nameThe name of the data set on which the I/Ooperation was being performed.

page-numberThe page number, in hexadecimal format, of thepage on which the I/O operation was beingperformed.

aa, bbbb, cccc, and ddddddddddddddddError information that is returned by the mediamanager and used for error analysis by IBMSoftware Support.


System actionThe system action depends on the value of function. Inmost cases, Db2 returns a message that indicates thata resource is unavailable with a reason code thatidentifies the problem. However, in the followingcases, the I/O-error page range of the data set isupdated and message DSNU086I is issued:

• function is WRITE• function is READ and the I/O operation was

performed during a restart or rollback operation.

After being issued 10 times for a given data set, thismessage is disabled for that data set until the data setis closed and reopened.


System programmer responseSee the information for the reason code that isreturned in the SQLCA or in the utility messages andtake the specified action.

If you suspect an error in Db2, see the informationabout collecting data.

Problem determinationSee the information about problem determination forthe reason code that is returned in the SQLCA or in theutility messages.

Check the MVS console log for an IOS (I/O subsystem)error message that indicates the type of I/O error thatoccurred. If an IOS message was issued, follow theproblem determination directions for that message.

Collect the following diagnostic items:



.

Related conceptsDb2 reason codes (Db2 Codes)Related tasksCollecting diagnostic data (Collecting data)Related informationDSNU086Icsect-name ttttt I/O ERRORS ON SPACE=dddddddd. DATA SET NUMBER= nnn. I/OERROR PAGE RANGE= aaaaaa, bbbbbb.

DSNB225I csect-name- BUFFER MANAGERI/O ERROR DURING function,DSNAME = data-set-name , MMERROR CODES=X'aaaaaaaa' DB2REASON CODE=X'reason-code'

ExplanationDb2 encountered an I/O error.


functionThe function that was being performed when theerror occurred. Possible values are READ, WRITE,CASTOUT, or FORMAT.

data-set-nameThe name of the data set on which the I/Ooperation was being performed.

aaaaaaaaError information that is returned by the mediamanager at the time of the failure. This informationused for error analysis by IBM Support.

reason-codeThe Db2 reason code value that indicates thereason for the failure. For explanations of reasoncodes, see Db2 reason codes (Db2 Codes).

System actionExcept for a castout error, the application terminateswith abend X'04E' and reason code 00C200A4 or00C200C0. If an error occurs during a castoutoperation, processing continues.


See the information for the given reason code and takethe specified action.

System programmer responseIf you suspect an error in Db2, see the informationabout collecting data.

Problem determinationCheck the MVS console log for an IOS (I/O subsystem)error message that indicates the type of I/O error thatoccurred. If an IOS message was issued, follow theproblem determination directions for that message.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_reasoncodes.html








.

Related conceptsDb2 reason codes (Db2 Codes)Related tasksCollecting diagnostic data (Collecting data)Related information00C200A4 (Db2 Codes)00C200C0 (Db2 Codes)

DSNB226I csect-name - BUFFER MANAGERPAGE GET ROUTINE DETECTED ANINVALID PAGE INDBNAME=database-name,SPACENAME=space-name ,INSTANCE=instance-number,DATA SET NUMBER= data-set-number, PAGEEXPECTED=X'expected page-number', PAGE NUMBERFOUND=X'page-number'

ExplanationAn unexpected page was received during buffermanager (BM) get page processing.


database-nameThe name of the database that contains theinvolved page set.

space-nameThe name of the table space or index space for theinvolved page set.


data-set-numberThe data set number for the involved page set.

expected page-numberThe page number of the page in error. The buffermanager expected to find this page in the buffer.

page-numberThe page number of the page that was found in thebuffer instead of the expected page.

System actionThe application is terminated with abend X'04E' andreason code 00C200F7.


See the information for the given reason code and takethe specified action.

System programmer responseIf you suspect an error in Db2, see the informationabout collecting data.







• DSN1COPY-generated copy of the table and index,taken before any recovery is performed.

.

Related conceptsDb2 reason codes (Db2 Codes)Related tasksCollecting diagnostic data (Collecting data)Related information00C200F7 (Db2 Codes)

DSNB227I csect-name - DFHSM RECALLFAILED FOR DSNAME=dataset-name HSMRC=return-codeHSMRSN=reason-code




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00c200a4.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00c200c0.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00c200f7.html

ExplanationThe attempt to recall a migrated data set failed.


dataset-nameThe name of the data set.

return-codeThe return code issued by DFSMShsm. This valuecorresponds to a similarly numbered MVS ARCmessage:

ARC11 + return-code + I

reason-codeThe reason code issued by DFSMShsm.

System actionA "resource not available" code is returned.


System programmer responseUse the information provided in message DSNB227I todetermine the reason for the DFSMShsm recall failure.

Related conceptsRECALL command (z/OS DFSMShsm StorageAdministration Reference)Related referenceARC messages (MVS System Messages)Related informationReturn codes from DFSMShsm commands(DFSMShsm Managing Your Own Data)

DSNB228I csect-name GROUP BUFFER POOLgbpname CANNOT BE ACCESSEDFOR function MVS IXLCACHEREASON CODE=reason

ExplanationWhile accessing group buffer pool gbpname forfunction function Db2 received an error from the z/OSMVS IXLCACHE request.function

READ or WRITEreason

Reason code from the z/OS MVS IXLCACHErequest

System actionThe system action depends on the function beingperformed and the reason code from the IXLCACHErequest.

If the reason code from the IXLCACHE request isX'0C121052', Db2 might abnormally terminate.

If the reason code from the IXLCACHE request is notX'0C121052', and the function is a WRITE, or a READperformed during rollback or Db2 restart, the page isadded to the logical page list (LPL) for the data set andmessage DSNB250E is issued.

Otherwise, a resource unavailable message is returnedto the user with a reason code that identifies thespecific problem.

System programmer responseIf the problem persists, and the problem affects asingle LPAR, restart Db2 on another LPAR.

Related conceptsRestart light (Db2 Data Sharing Planning andAdministration)Related referenceIXLCACHE — Cache ServicesReturn and Reason Codes for IXLCACHEREQUEST=WRITE_DATAReturn and Reason Codes for IXLCACHEREQUEST=WRITE_DATALIST

DSNB229I csect-name UNEXPECTED ERRORWHEN CHECKING FOR REQUESTCOMPLETION FOR GROUP BUFFERPOOL gbp-name MVS IXLFCOMPREASON CODE=reason

ExplanationDb2 received an unexpected error from MVS whenchecking for the completion of a write request to thesecondary group buffer pool for duplexing. gbp-nameindicates the name of the group buffer pool. If thegroup buffer pool is duplexed and the error wasencountered on a request to the secondary groupbuffer pool, then gbp-name indicates the name of thegroup buffer pool suffixed with '-SEC'.

reason is the reason code from the MVS IXLFCOMPservice.

System actionDb2 returns the group buffer pool back to simplexmode. The secondary group buffer pool is deallocated.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.arcf000/hr1023.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.arcf000/hr1023.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieam200/zmsgs.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.arcd000/extenrc.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.arcd000/extenrc.htm

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_restartlightds.html


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai700/cache.htm

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai700/ieai700377.htm




System programmer responseSee z/OS MVS Programming: Sysplex ServicesReference for an explanation of the MVS IXLFCOMPreason code.

DSNB232I csect-name - UNEXPECTED DATASET LEVEL ID ENCOUNTERED -LEVEL ID =lvlid EXPECTED LEVELID=xlvlid DSN=dsn

ExplanationA required data set of a Db2 table space could not beopened. Db2 encountered an unexpected data setlevel ID.lvlid

The unexpected level ID from the data set. If Db2was unable to retrieve the level ID from the dataset (for example, if the data set had been deletedand redefined), the level ID is shown as "X''".

xlvlidThe level ID recorded by Db2 previously and is theexpected level ID for opening the data set

dsnThe DSNAME of the data set.

This problem could be the result of data sets that wererestored to a level that is inconsistent with other datasets, inconsistent with the Db2 log, or both.

System actionDb2 sends back a 'resource unavailable' SQL code tothe application and a reason code explaining the error.


System programmer responseTo enable access to a data set reported as down level,take one of the following actions:

• Restore the page set or partition to the proper level(use DSN1COPY, DFHSM, or another tool).

Identify the level ID of a copy of the page set orpartition by running the DSN1PRNT(FORMAT) utility.The level ID is found in the header page of the pageset or partition.

• Recover the down level page set or partition tocurrency by running the RECOVER or RECOVERLOGONLY utility.

• Accept the down levelling by running the REPAIRutility with the LEVELID option.

This option is only valid if Db2 is able to access thelevel ID (lvlid is not "X''").

Inconsistent data problems might result from thisaction and are the user's responsibility.

• Replace the contents of the page set or partitionusing the LOAD REPLACE utility.

• Explicitly restore the page set to a prior point in timewith the RECOVER utility.

If the expected level ID is less than the encounteredlevel ID, it is possible that the object identified in themessage was ported from another system improperlyor it might indicate that DSNDB01.SYSLGRNX is downlevel. If the problem is in the object identified in themessage, the actions listed above can be used to allowaccess to the data. If the problem is in SYSLGRNX, thisis a serious situation that compromises therecoverability of all objects managed by Db2.Investigate whether SYSLGRNX might haveinadvertently been restored to a point in timeinconsistent with the rest of the Db2 system.

DSNB233I csect-name DBNAME database-name SPACENAME space-nameINSTANCE instance-numberPARTITION partition-number IS INBASIC PAGE FORMAT ANDSHOULD BE CONVERTED TOEXTENDED PAGE FORMAT

ExplanationThis message is issued upon a physical open of a tablespace or index. The specified partition is still in thebasic LRSN format and makes Db2 susceptible tooutages if this 6-byte limit is exceeded. It is stronglyrecommended to convert it to the extended LRSNformat to prevent the 6-byte limit being exceeded.


database-nameThe database name.

space-nameThe name of the table space or index space.

intance-numberThe instance number.

partition-numberThe partition number that remains in 6-byteformat.

System actionProcessing continues. This message is shown as manyas 20 times each time that Db2 is started, and it is notshown when utilities open the page sets. Absence of


this message does not imply all table spaces havebeen converted, but rather no table spaces have beenopened in the 6-byte format.

System programmer responseRun the REORG or REBUILD utility to convert the tablespace or index to 10-byte LRSN format, as describedin Converting page sets to the 10-byte RBA or LRSNformat (Db2 Administration Guide).



Related conceptsThe extended 10-byte RBA and LRSN in Db2 11(Db2 for z/OS What's New?)Related tasksWhat to do before RBA or LRSN limits arereached (Db2 Administration Guide)

DSNB235A csect-name - GRS RESOURCESHORTAGE DETECTED BY DB2

ExplanationA z/OS Global Resource Serialization (GRS) resourceshortage was detected when Db2 opened or closed adata set.


System actionTo relieve the GRS resource shortage, Db2 might closedata sets that have not been used recently.


Message DSNB235A is deleted when Db2 detects thatthe GRS resource shortage has been relieved.

System programmer responseWork with your Db2 administrator to reduce the Db2workload, or reduce the number of open data sets.

Problem determinationGRS message ISG353E might be displayed when theresource shortage occurs. This message identifies thespecific storage area that has a shortage.

GRS message ISG354I displays when the resourceshortage has been relieved.

Related referenceMessage ISG353E (MVS System Messages)Message ISG354I (MVS System Messages)

DSNB250E csect-name A PAGE RANGE WASADDED TO THE LOGICAL PAGELIST. DATABASE NAME=database-name, SPACE NAME=space-name,INSTANCE=instance-number,DATA SET NUMBER=data-set-number, PAGE RANGE X'low-page'TO X'high-page', STARTLRSN=X'start-lrsn', ENDLRSN=X'end-lrsn', STARTRBA=X'start-rba', LPL TRACEID=trace-id, LPL REASONTYPE=reason-type

ExplanationDB2 added a page range to the logical page list (LPL)for the specified data set, because the pages in thepage range had a problem.


database-nameThe name of the database.



data-set-numberThe data set number.

low-page and high-pageThe range of pages that was added to the LPL. Thevalues are hexadecimal page numbers.

start-lrsn and end-lrsnThe log range that is needed to recover the pagesin the page range. These values are RBA valuesunless DB2 is in a data sharing environment. Inthat case, these values are LRSN values. A zerovalue for end-lrsn refers to the current end of therecovery log.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_convertingtoextended.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_convertingtoextended.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/wnew/src/tpc/db2z_aboutexpandedrbalrsn.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_rbalrsnlimitsreached.html


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieam900/je022404.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieam900/je022304.htm

start-rbaIn a data sharing environment, the starting RBAvalue of the recovery log range if the value is notzero. The start-rba value applies to log records foronly the DB2 member that issued the message.

trace-idA value that is used for serviceability by IBMSupport.

reason-typeThe reason why the pages were added to the LPL.reason-type can contain one of the followingvalues:DASD

Db2 encountered a DASD I/O error when tryingto read or write pages on DASD.

LOGAPPLYDb2 cannot apply log records to the pages.

GBPDb2 cannot successfully read from orexternalize the pages to the group buffer pool.This problem occurred for one of the followingreasons:

• a link or structure failure• the group buffer pool is in rebuild status• the group buffer pool was disconnected

LOCKDB2 cannot get the required page latch or pageP-lock on the pages.

CASTOUTThe Db2 castout processor cannot successfullycast out the pages.

NOTLOGGDWork on an object needs to be undone.However, the work was not logged, becausethe object has the NOT LOGGED attribute.

System actionThe pages are added to the LPL

For any reason-type value other than NOTLOGGD, Db2initiates the automatic LPL recovery. The pages remaininaccessible until they are recovered.

If you attempt to access a page in the LPL, Db2 returnsSQLCODE -904 with reason code 00C20206.

If MVS detects a problem when accessing the groupbuffer pool, DB2 writes a SYS1.LOGREC entry thatdescribes the error.

System programmer responseTake the appropriate actions for the reason-type valuebased on the console message.

To recover pages from the LPL, perform one of thefollowing actions:

• For a reason-type value other than NOTLOGGD, issuethe START DATABASE command with the SPACENAMoption.

• Run the RECOVER utility• Run the LOAD utility

Related reference-START DATABASE (Db2) (Db2 Commands)RECOVER (Db2 Utilities)LOAD (Db2 Utilities)Related information-904 (Db2 Codes)00C20206 (Db2 Codes)

DSNB260I csect-name WARNING - A READERHAS BEEN RUNNING FOR durationMINUTES - CORRELATIONNAME=correlation-name,CONNECTION ID=connection-id,LUWID=luwid ID=token, PLANNAME=plan-name,AUTHID=authorization-id, ENDUSER ID=user-id, TRANSACTIONNAME=transaction-name,WORKSTATION NAME=system-name

ExplanationOne of the following situations occurred:

• A long-running reader reached the maximumpermitted time without issuing either a COMMIT orROLLBACK statement.

• A reader that was claimed by cursors that weredefined WITH HOLD was held longer than thenumber of minutes that an agent can hold a readclaim.


durationThe time, in minutes, that has elapsed since thebeginning of the unit of work.

correlation-nameThe correlation name that is associated with theunit of work.

connection-idThe connection ID that is associated with the unitof work.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_startdatabase.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_recover.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_load.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/n904.html


luwidThe logical unit of work ID, or an asterisk (*) todenote that the thread originated at the local site.

tokenA unique token number that is associated with thelogical unit of work ID.

plan-nameThe plan that is associated with the unit of work.

authorization-idThe authorization ID that is associated with theunit of work.

user-idThe user ID that is associated with the unit ofwork, if known. Otherwise, an asterisk (*).

transaction-nameThe transaction that is associated with the unit ofwork, if known. Otherwise, an asterisk (*).

system-nameThe workstation host name that is associated withthe unit of work, if known. Otherwise, an asterisk(*).

The amount of time that is permitted for a reader iscontrolled by the LRDRTHLD subsystem parameter.


If IFCID 0313 trace is activated, an IFCID 0313 tracerecord is written. This message is issued every timethat the threshold is reached.

System programmer responseWork with the application programmer to determine ifthere is a problem with the unit of work. If anapplication program caused the unit of work to reachits time limit threshold, you can use CANCEL THREADto cancel the associated thread.

Administrator responseIncrease the value of subsystem parameter LRDRTHLDso that this message is issued less frequently.

Programmer responseMake sure that the application commits at appropriateintervals, or work with the Db2 administrator todetermine an appropriate frequency for the COMMITcheck.

Related conceptsCommit and rollback of transactions(Introduction to Db2 for z/OS)

Related referenceLONG-RUNNING READER field (LRDRTHLDsubsystem parameter) (Db2 Installation andMigration)-CANCEL THREAD (Db2) (Db2 Commands)COMMIT (Db2 SQL)ROLLBACK (Db2 SQL)

DSNB301E csect-name GROUP BUFFER POOLgbp-name CANNOT BECONNECTED DB2 REASON CODE =reason-code MVS IXLCONNREASON CODE = ixlconn-reason

ExplanationDb2 was not able to connect to the named groupbuffer pool. This message is generally issued once foreach Db2 subsystem for each Db2 reason code, except00C20204, until the failure condition is corrected.csect-name


gbp-nameThe name of the group buffer pool.

reason-codeThe Db2 reason code.

For Db2 reason code 00C20204, which indicates aproblem during MVS IXLCONN processing, theDSNB301E message is issued once for each Db2subsystem for each IXLCONN reason code until thefailure condition is corrected.

ixlconn-reasonWhen the Db2 reason code is 00C20204, the MVSIXLCONN reason code. For all other Db2 reasoncode values, ixlconn-reason contains zeros.

System actionIf the connection was requested on behalf of anaccess request by an SQL user on this Db2, SQLCODE-904 (resource unavailable) is returned to the SQLuser with the Db2 reason code shown in this message.

If the connection was requested on behalf of an SQLuser on another Db2 in the data sharing group,SQLCODE -904 (resource unavailable) is returned tothe SQL user with Db2 reason code 00C20252. Thisindicates that the requested table space or indexspace is unavailable because another Db2 cannotconnect to the group buffer pool.

If the MVS IXLCONN reason code is xxxx0C08(structure allocation failed because there was nosuitable facility to allocate based on the preference listin the MVS CFRM administrative policy), or if the MVS


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_commitandrollbackoftransactions.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_commitandrollbackoftransactions.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_lrdrthld.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_cancelthread.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_commit.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_rollback.html

IXLCONN reason code is xxxx084C (user does not haveproper Security Access Facility (SAF) authorization),then IFCID 0250, if active, contains additionaldiagnostic information.

System programmer responseSee the specified Db2 reason code for informationabout appropriate actions.

Related referenceReturn and Reason CodesRelated information-904 (Db2 Codes)00C20204 (Db2 Codes)00C20252 (Db2 Codes)00C202A8 (Db2 Codes)

DSNB302I csect-name GROUP BUFFER POOLgbpname IS ALLOCATED IN AVOLATILE STRUCTURE

ExplanationThe Db2 group buffer pool structure is volatile.

One Db2 member issues this message whenever thestructure has the volatile attribute. Db2 detects thiseither on the first connection to the group buffer poolor when the attribute changes later. Db2 alwaysrequests nonvolatile group buffer pools but allowsallocation in a volatile structure if that is all that isavailable.

System actionDb2 processing continues.

System programmer responseTo cause the group buffer pools to be allocated innonvolatile coupling facilities, ensure that:

• At least a subset of your coupling facilities areconfigured correctly for nonvolatility.

• The MVS CFRM policy correctly specifies thenonvolatile coupling facilities in the preference listfor the group buffer pool coupling facility structures.

Even when these things are correctly done, theremight be instances when a suitable coupling facility inthe preference list cannot be found (for example, notenough free space), and therefore allocation occurs ina different coupling facility. MVS tries to allocate thestructure in the facility that best meets the structureallocation request as follows:

1st choice:Coupling facility that meets the volatilityrequirement, the space requirement, and theexclusion list requirement.

2nd choice:Coupling facility that meets the volatilityrequirement and the storage requirement.

3rd choice:Coupling facility that has the best fit (mostavailable free space) even though this might beless than the amount requested.

4th choice:Structure cannot be allocated.

IFCID 0250, if activated, contains a list of the couplingfacilities on which allocation was attempted.

DSNB303E csect-name A LOSS OFCONNECTIVITY WAS DETECTEDTO GROUP BUFFER POOL gpbname

ExplanationConnectivity to group buffer pool gpbname was lost.

System actionDb2 disconnects from the coupling facility structurewith REASON=FAILURE.

The action taken in response to this problem dependson the attempted function, as follows:

• For a coupling facility read: SQLCODE -904 (resourceunavailable) is returned to the SQL user with areason code indicating the specific error.

• For a coupling facility read during rollback, backout,or restart: The inaccessible page is added to thelogical page list (LPL) for the page set. MessageDSNB250E is issued for the first page of each dataset added to the LPL.

• For a coupling facility read during castout: Thecastout operation cannot complete.

• For a coupling facility write: The changed page isadded to the LPL for the page set.

DSNB304I csect-name GROUP BUFFER POOLgbpname WAS SET TO 'DAMAGEASSESSMENT PENDING' STATUS

ExplanationA coupling facility structure for a group buffer pool wasdamaged.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieai700/ieai700392.htm




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00c202a8.html

System action• Db2 puts the group buffer pool into 'damage

assessment pending' (DAP) status. MessageDSNB304I indicates the DAP status. The groupbuffer pool cannot be accessed until DAP status iscleared.

• The Db2 damage assessment process determineswhich table spaces and index spaces are using thefailed group buffer pool and puts those spaces into'group buffer pool recovery pending' (GRECP) status.

• After Db2 sets all the necessary spaces to GRECPstatus, the DAP status for the group buffer pool iscleared. Message DSNB305I indicates that DAPstatus is cleared.

DSNB305I csect-name 'DAMAGEASSESSMENT PENDING' STATUSWAS CLEARED FOR GROUPBUFFER POOL gbpname

ExplanationDamage assessment completed and the 'damageassessment pending' (DAP) status is cleared for thegroup buffer pool (GBP). At this point, the group bufferpool status is no longer restricted and Db2 attempts toreconnect to the group buffer pool on the nextreference to a GBP-dependent page set within theassociated buffer pool.

Message DSNB304I precedes this message.

DSNB306I csect-name THE REQUESTEDLENGTH OF THE LOCAL CACHEVECTOR COULD NOT BEALLOCATED FOR GROUP BUFFERPOOL gbpname REQUESTEDLENGTH = length1 ALLOCATEDLENGTH = length2

ExplanationDb2 connected to the group buffer pool indicated bygbpname, but the MVS Cross-system ExtendedServices (XES) component could not allocate therequested size of the local cache vector (LCV) in thehardware system area (HSA). Db2 requires an LCV sizethat is large enough to handle all pages in themember's buffer pool.

length1 indicates the LCV size (in number of bits) thatDb2 requested. length2 indicates the LCV size (innumber of bits) that XES was able to allocate.

To prevent flooding the operator console, this messageis only issued once per Db2 member per group bufferpool until the condition is corrected.

System actionDb2 disconnects from the GBP and issues messageDSNB301E with reason code 00C20208, if it has notyet been issued.

SQLCODE -904 is returned to the user with a reasoncode of 00C20208.

System programmer responseThere is not enough HSA storage on the processor tosupport the size of the local cache vector. The detailsof HSA allocation are machine-dependent and aredefined by the hardware. To correct this problem, takeone or both of the following actions:

• Consult the documentation for your processorhardware to determine if the HSA storage allocationcan be increased, and if so, how to do it.

• Modify the software configuration in your parallelsysplex to reduce the number or size of the vectorsthat are in use by other coupling facility structureusers. Consider the following possible solutions:

– Use the Db2 ALTER BUFFERPOOL command toreduce the size of this local buffer pool. Thismeans that you might have to reduce the size ofthe virtual pool.

– Use the Db2 ALTER BUFFERPOOL command toreduce the size of another local buffer pool that isalready connected to a group buffer pool. Thismeans that you might have to reduce the size ofthe virtual pool. If you make a connected bufferpool smaller, Db2 can usually contract the size ofthe corresponding LCV dynamically, making HSAstorage available. However, Db2 cannot always dothe dynamic LCV contraction. In cases where Db2cannot dynamically contract the LCV size, you canuse the Db2 ALTER BUFFERPOOL command toeither force a deallocation of the LCV or to force acontraction of the LCV as follows:

1. Redefine the virtual pool to be smaller than theoriginal size.

2. Take one of the following actions:

a. Make the virtual pool very small (perhaps50 pages or less). Making the virtual poolsufficiently small should let Db2dynamically contract the LCV, or

b. Delete the virtual pool to let Db2 disconnectfrom the group buffer pool. This frees theentire LCV associated with that member'sconnection to that group buffer pool.

– Consolidate your group buffer pool-dependentpage sets into fewer buffer pools to reduce thenumber of group buffer pool connections.


– Consult the documentation for the other softwarecomponents that might be using a coupling facilitycache or list structure with an associated LCV todetermine whether it is possible to either deletethe connection or to reduce the size of the LCVassociated with the connection.

DSNB307I csect-name GROUP BUFFER POOLgbpname WAS SUCCESSFULLYALLOCATED BUT THE EXCLUSIONLIST WAS NOT HONORED

ExplanationDb2 successfully connected to the group buffer pooland allocated the group buffer pool in a couplingfacility. However, the group buffer pool was allocatedin a coupling facility containing a structure in theexclusion list.

System programmer responseIf you require that the exclusion list be honored, youmust ensure that there is sufficient space in thecoupling facilities that are not in the exclusion list.IFCID 0250 provides information about which facilitieswere attempted.

DSNB308I csect-name GROUP BUFFER POOLgbpname WAS SUCCESSFULLYALLOCATED BUT THE ALLOCATEDSIZE OF alloc_size IS LESS THANTHE REQUESTED SIZE OF req_size

ExplanationDb2 successfully connected to the group buffer pooland allocated the group buffer pool in a couplingfacility. However, the allocated size of the group bufferpool was less than the requested size in the MVSCFRM administrative policy because there is notenough space in the preference list facilities. Bothalloc_size and req_size are in 4KB blocks.

System programmer responseIFCID 0250 provides information about which couplingfacilities were used for attempted allocation.

DSNB309I csect-name GROUP BUFFER POOLgbpname HAS BEENDISCONNECTED WITH A REASONOF 'reason'

ExplanationDb2 disconnected from the named group buffer pool.

reason indicates one of the following values:

NORMALDb2 disconnected the group buffer pool normally.MVS deletes the connection.

FAILUREDb2 disconnected the group buffer poolabnormally. MVS puts the connection into a 'failed-persistent' state. Db2 disconnects the GBP with areason of FAILURE when some type of error hasbeen detected, and castout processing cannotproceed. Usually the error involves a connectivityfailure to either the coupling facility or DASD. Thismessage is preceded by message DSNB303E, andprobably a series of DSNB311I and DSNB312Imessages.

If this message is issued because connectivity was lostto the group buffer pool, this message signifies thatthis Db2 member has completed its processing of theerror.

System programmer responseSee the system programmer response for messageDSNB311I or DSNB312I.

DSNB310I csect-name GROUP BUFFER POOLgbpname IS ALLOCATED IN ANONVOLATILE STRUCTURE

ExplanationThe coupling facility storage in which the group bufferpool is allocated was previously volatile, but is nownonvolatile. For availability reasons, we recommendthat Db2 group buffer pools be allocated in nonvolatilecoupling facility storage. When Db2 connects a groupbuffer pool, it requests that the backing couplingfacility structure be allocated in nonvolatile storage. Ifthe request for nonvolatile storage is not honored, Db2issues message DSNB302I.


DSNB311I csect-name DBNAME database-name SPACENAME space-nameINSTANCE instance-number HASPAGES IN THE LOGICAL PAGE LIST

ExplanationThis message is issued after a loss of connectivity to agroup buffer pool is detected. The named table spaceor index space has one or more pages in the logicalpage list (LPL) that need to be recovered. Thismessage is issued after Db2 has completed itsprocessing for the table space or index space; this


point is the earliest point at which you can recover LPLpages for that table space or index.





System actionThe pages in the LPL are not accessible until they havebeen recovered.

System programmer responseIssue the START DATABASE command with the namedtable space or index to recover the LPL pages. Youmust issue the START DATABASE command from aDb2 member that can connect to the group bufferpool. Alternatively, you can use the RECOVER utility orthe LOAD utility to recover the LPL pages.

Related reference-START DATABASE (Db2) (Db2 Commands)RECOVER (Db2 Utilities)LOAD (Db2 Utilities)

DSNB312I csect-name DBNAME database-name SPACENAME space-nameINSTANCE instance-numberPARTITION partition-number HASPAGES IN THE LOGICAL PAGE LIST

ExplanationThis message is issued after a loss of connectivity to agroup buffer pool is detected. A partition of the namedtable space or index has one or more pages in thelogical page list (LPL) that need to be recovered. Thismessage is issued after Db2 has completed itsprocessing for the partition; this point is the earliestpoint at which you can recover the LPL pages for thatpartition.





partition-numberThe partition number.

System actionThe pages in the LPL are not accessible until they havebeen recovered.

System programmer responseIssue the START DATABASE command on the tablespace or index space partition to recover the LPLpages. You must issue the START DATABASE commandfrom a Db2 member that can connect to the groupbuffer pool. Alternatively, you can use the RECOVERutility or the LOAD utility to recover the LPL pages.

Related reference-START DATABASE (Db2) (Db2 Commands)RECOVER (Db2 Utilities)LOAD (Db2 Utilities)

DSNB313I csect-name GROUP BUFFER POOLgpbname TO BE DISCONNECTEDREASON=reason LOSSCONNPERCENTAGE=percentage

ExplanationThis Db2 member is disconnecting from group bufferpool gpbname because it has lost connectivity to thecoupling facility in which the group buffer pool isallocated.

reason is one of the following:NOSFMPOL

MVS cannot determine the scope of the loss ofconnectivity because there is no active SFM policywith CONNFAIL(YES).

LOSSCONNMVS determined that the scope of the loss ofconnectivity was less than 100%.

NOXESEVLMVS started to try to determine the scope of theloss of connectivity, but some condition occurredwhich prevented MVS from being able to completethe evaluation. One example of such a condition








would be that the SFM policy became inactivewhile MVS was trying to do the evaluation.

If reason is LOSSCONN, then percentage indicates thepercentage of lost connectivity that was calculated byMVS. MVS evaluates the scope of the loss ofconnectivity in terms of SFM weights associated withthe systems which have lost connectivity and whichhave active connectors to the coupling facilitystructure (if there are systems that do not have anactive connector to the coupling facility structure, thenthose systems are not factored into the "percentageloss of connectivity" calculation).

If reason is not LOSSCONN, then percentage is notapplicable (it should appear as zero).

System actionThe Db2 member disconnects the group buffer pool,putting its connection into a "failed-persistent" state.

If there are transactions that are in progress at thetime of the connectivity failure, Db2 might need to addpages to the logical page list (LPL).

System programmer responseUse the START DATABASE command to recover theLPL pages. If DSNDB01 or DSNDB06 objects have LPLpages, you might need to recover these first, beforeproceeding with LPL recovery for other objects.

DSNB314I csect-name DAMAGEASSESSMENT TO BE TRIGGEREDFOR GROUP BUFFER POOLgpbname REASON=reason

ExplanationDb2 is about to initiate the damage assessmentfunction for group buffer pool gpbname because of adetected error in either the coupling facility in whichthe group buffer pool was allocated, or in theconnectivity from the MVS systems to the couplingfacility.

reason is one of the following:100%LCON

An error has occurred in a coupling facility or in theattachments of MVS systems to a coupling facilitywhich has caused all Db2 members to loseconnectivity to the named group buffer pool.

STRFAILThere was an error in the coupling facility in whichthe group buffer pool was allocated which causeda failure of the coupling facility structure.

CONERRORThe named group buffer pool is currently allocatedin a coupling facility, but Db2 cannot connect tothe group buffer pool because the system on whichit is running does not currently have connectivity,and MVS has indicated that currently no othermember is actively connected and hasconnectivity.

DAPThe named group buffer pool is in damageassessment pending (DAP) state.

System actionDb2 triggers the damage assessment function toensure that any changed pages that might have beencached in the affected group buffer pool get marked as"needing recovery" (the objects to which the pagesbelong are marked in GRECP state). This messageshould be immediately followed by a DSNB304Imessage indicating that the group buffer pool hasbeen entered into damage assessment pending (DAP)state.

If there are transactions that are in progress at thetime of the connectivity failure, Db2 might need to addpages to the logical page list (LPL).

There is one case where Db2 triggers damageassessment for a group buffer pool, but no DSNB314Imessage is issued. This case is where the group bufferpool was manually deleted (via MVS SETXCF FORCEcommands) while all connections to the group bufferpool were failed-persistent (e.g. all Db2 memberswere down). In this case, the next Db2 member toconnect to the group buffer pool will cause MVS to tryto reallocate a new instance of the group buffer pool insome coupling facility in the CFRM policy preferencelist. If the allocation succeeds, then Db2, by doing acoupling facility structure version id comparison, willdetect that the previous instance of the group bufferpool had been lost, and will trigger damageassessment. But you will not receive the DSNB314Imessage in this case, nor will you receive theDSNB304I or DSNB305I messages indicating that thegroup buffer pool has been put into damageassessment pending (DAP) state. You will only receivea series of DSNB322I and/or DSNB323I messagesindicating those pagesets or partitions that have beenput into GRECP state by the damage assessmentprocess.

System programmer responseUse the START DATABASE command to recover theLPL pages and GRECP objects. If DSNDB01 orDSNDB06 objects are in GRECP state or have LPLpages, you might need to recover these first, before


proceeding with GRECP or LPL recovery for otherobjects.

DSNB315I csect-name GROUP BUFFER POOLgpbname IS ALLOCATED ASGBPCACHE cacheatt

ExplanationYES

The group buffer pool will be used for datacaching.

NOThe group buffer pool will not be used for datacaching. It will be used for cross invalidation only.

One Db2 member issues this message whenever thestructure is allocated. Db2 detects this on the firstconnection to the group buffer pool either in themainline processing or during group buffer poolrebuild.


DSNB316I csect-name GROUP BUFFER POOLgbp-name DELETED BECAUSE OFSUBSYSTEM PARAMETERSETTING

ExplanationThe specified group buffer pool was deleted duringDb2 restart processing.


gbp-nameThe name of the group buffer pool that wasdeleted.

The group buffer pool is deleted when there are noother Db2 subsystems connected to it, if theDEL_CFSTRUCT_ON_RESTART subsystem parameterindicates that Db2 should attempt to delete all groupbuffer pools.

System actionThe group buffer pool named in the message isdeleted.


Related referenceDEL CF STRUCTS field(DEL_CFSTRUCTS_ON_RESTART subsystemparameter) (Db2 Installation and Migration)

DSNB317I NO OBJECTS IN GRECP STATUS

ExplanationNo objects were found in GRECP status.



Related conceptsNormal restart and recovery (Db2Administration Guide)Related referenceGroup buffer pool RECOVER-pending status(Db2 Utilities)

DSNB319A csect-name THERE IS A SHORTAGEOF SPACE IN GROUP BUFFERPOOL gbp-name

ExplanationThe amount of storage in the group buffer pool (GBP)coupling facility structure available for writing newpages is low. The GBP is 75 percent full with changeddata. As the GBP fills with changed data, the castoutthresholds are continuously reached, and the castoutengines must continuously work to attempt to keepthe number of changed pages in the GBP below thecastout thresholds. Also, the more changed data theGBP contains, the less efficiently it operates.Completely running out of GBP storage can result intransaction delays and in pages being added to thelogical page list (LPL).



This message might not be automatically deleted in apre SP5.2.1-JES3 environment.

Operator responseContact the system programmer to fix the storageproblem.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_delcfstructsonrestart.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_normalrestart.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_grouprecoverpendingstatus.html


System programmer response

You can relieve the GBP storage shortage by takingone or more of the following actions:

• Use the ALTER GROUPBUFFERPOOL command tolower the CLASST and GBPOOLT castout thresholds.

• Use the ALTER GROUPBUFFERPOOL command tolower the GBPCHKPT GBP checkpoint frequency.

• Use the MVS SETXCF START,REBUILD command toexpand the GBP coupling facility structure. If yourebuild, you can use the ALTER GROUPBUFFERPOOLcommand to lower the RATIO so that a higherpercentage of the GBP storage is given to dataentries over directory entries.

• If you are running on MVS 5.2 or a subsequentrelease, you can use the MVS SETXCF START,ALTERcommand to expand the size of the GBP (themaximum size to which you can expand isdetermined by the SIZE parameter in the CFRMpolicy that was used to allocate the GBP).

If you don't do anything to relieve the storageshortage, message DSNB325A appears if the GBPreaches 90 percent full.

Message DSNB327I appears when the GBP storageshortage is relieved.

You can monitor the amount of GBP storage in usewith the DISPLAY GBPOOL command and with the Db2statistics trace. Monitor the castout activity to ensurethat castouts are keeping up with the rate of GBP-writeactivity. You can use Performance trace classes 20 and21 (specifically, IFCIDs 0261, 0262 and 0263) to domore detailed monitoring of the Db2 castoutprocessing.

DSNB320I csect-name DBNAME database-name SPACENAME space-nameINSTANCEinstance-numberPARTITION partition-number INGROUP BUFFERPOOL pool-nameIS IN GROUP BUFFERPOOLRECOVERY PENDING STATE

ExplanationThe named table space or index space partition is ingroup buffer pool recovery pending (GRECP) status.






pool-nameThe name of the group buffer pool.

System actionThe data in the named partition is not accessible.

User responseIssue the START DATABASE command on the partitionto remove the GRECP status and make the dataaccessible again. You can also use the RECOVER orLOAD utility with the REPLACE option to clear theGRECP status.

Severity4 (warning)

Related reference-START DATABASE (Db2) (Db2 Commands)RECOVER (Db2 Utilities)LOAD (Db2 Utilities)Group buffer pool RECOVER-pending status(Db2 Utilities)

DSNB321I csect-name DBNAME database-name SPACENAME space-nameINSTANCE instance-number INGROUP BUFFERPOOL pool-nameIS IN GROUP BUFFERPOOLRECOVERY PENDING STATE

ExplanationThe named table space or index space is in groupbuffer pool recovery pending (GRECP) status.





pool-nameThe name of the group buffer pool.







System actionThe table space or index space is not accessible.

User responseIssue the START DATABASE command on the partitionto remove the GRECP status and make the dataaccessible again. You can also use the RECOVER orLOAD utility with the REPLACE option to clear theGRECP status.

Severity4 (warning)


DSNB322I csect-name - TABLE SPACE ORINDEX SPACE WITH DBID X'dbid'PSID X'psid' PARTITION part-number IN GROUP BUFFERPOOLgbpname IS IN GROUPBUFFERPOOL RECOVERYPENDING STATE AND CANNOT BEAUTOMATICALLY RECOVERED

ExplanationThis message reports the group buffer pool recoverypending (GRECP) status of the table space or indexspace partition identified by the internal identifiersDBID and PSID. This message is issued instead ofmessage DSNB320I when the name of the table spaceor index space is not available. The partition cannot beautomatically recovered because there are retainedphysical locks (P-locks) on the partition.

System actionThe data in the identified partition is not accessible.

User responseIssue the -DISPLAY DATABASE(*) SPACENAM(*)RESTRICT command to determine the table spaces orindex spaces partition in GRECP status. First, start thefailed Db2 members that hold retained P-locks on thepartition.Issue the -START DATABASE command onthe partition to remove the GRECP status and makethe data accessible again. You can also use theRECOVER or LOAD utility with the REPLACE option toclear the GRECP status.

Severity4 (warning)

DSNB323I csect-name - TABLE SPACE ORINDEX SPACE WITH DBID X'dbid'PSID X'psid' IN GROUPBUFFERPOOL gbpname IS INGROUP BUFFERPOOL RECOVERYPENDING STATE AND CANNOT BEAUTOMATICALLY RECOVERED

ExplanationThis message reports the group buffer pool recoverypending (GRECP) status of the table space or indexspace identified by the internal identifiers DBID andPSID. This message is issued instead of messageDSNB321I when the name of the table space or indexspace is not available. The table space or index spacecannot be automatically recovered because there areretained physical locks (P-locks) on the space.

System actionThe table space or index space is not accessible.

User responseIssue the -DISPLAY DATABASE(*) SPACENAM(*)RESTRICT command to determine the table spaces orindex spaces in GRECP status. First, start the failedDb2 members that hold retained P-locks on the tablespace or index space.Issue the -START DATABASEcommand on the table space or index space to removethe GRECP status and make the data accessible again.You can also use the RECOVER or LOAD utility with theREPLACE option to clear the GRECP status.

Severity4 (warning)

DSNB325A csect-name THERE IS A CRITICALSHORTAGE OF SPACE IN GROUPBUFFER POOL gbp-name

ExplanationThe amount of storage in the group buffer pool (GBP)coupling facility structure available for writing newpages is critically low. The primary or secondary GBP is90 percent full with changed data. (A gbp-name thatends in SEC is a secondary GBP in a duplexingenvironment.)

As the GBP fills with changed data, the castoutthresholds are continuously reached, and the castoutengines must continuously work to attempt to keep







the number of changed pages in the GBP below thecastout thresholds. In addition, the more the GBP isfilled with changed data, the less efficient are thecoupling facility storage management algorithms.Completely running out of GBP storage can result intransaction delays and in pages being added to thelogical page list (LPL).



This message might not be automatically deleted in apre-SP5.2.1-JES3 environment.

Operator responseContact the system programmer to fix the storageproblem.

System programmer responseYou can relieve the GBP storage shortage by takingone or more of the following actions:

• Use the ALTER GROUPBUFFERPOOL command tolower the CLASST and GBPOOLT castout thresholds.

• Use the ALTER GROUPBUFFERPOOL command tolower the GBPCHKPT GBP checkpoint frequency.

• Use the MVS SETXCF START,REBUILD command toexpand the GBP coupling facility structure. If yourebuild, you can use the ALTER GROUPBUFFERPOOLcommand to lower the RATIO so that a higherpercentage of the GBP storage is given to dataentries over directory entries.

• If you are running on MVS 5.2 or a subsequentrelease, you can use the MVS SETXCF START,ALTERcommand to expand the size of the GBP (themaximum size to which you can expand isdetermined by the SIZE parameter in the CFRMpolicy that was used to allocate the GBP).

If you do not do anything to relieve the storageshortage, message DSNB228I appears if a write to theGBP fails due to a 'GBP full' condition. If Db2 detects a'full' condition, it will suspend the transaction, initiatecastout activity, and then retry the write to the GBP. Ifthe GBP write still fails after several retry attempts,then Db2 adds the page to LPL.

Message DSNB327I is displayed when the GBPstorage shortage is relieved.

You can monitor the amount of GBP storage in usewith the DISPLAY GBPOOL command and with the Db2statistics trace. Monitor the castout activity to ensurethat castouts are keeping up with the rate of GBP-write

activity. You can use Performance trace classes 20 and21 (specifically, IFCIDs 0261, 0262 and 0263) to domore detailed monitoring of the Db2 castoutprocessing.

DSNB327I csect-name GROUP BUFFER POOLgbp-name HAS ADEQUATE FREESPACE

ExplanationThe group buffer pool (GBP) coupling facility structurehas adequate space available for the writing of newpages to the GBP.

This message may be issued when either of thefollowing occurs:

• Rebuilding of GBP reduces changed page count to60% or less of GBP capacity.

• 'changed data.' entries decrease to 60% or lowerwhen they were previously 75% GBP capacity orhigher.


DSNB328I OBJECT NAME object-nameOBJECT ID X'object-id' REMAINSIN GRECP STATUS. USER ACTIONIS NEEDED TO RECOVER THEOBJECT

ExplanationDb2 left an object in GRECP status.

object-nameThe identifier of the object that was left in theindicated status. It uses one of the followingformats:

• db-name.space-name for table spaces and indexspaces.

• db-name.space-name.part-number if the objectis a partition within a table space or index space

Rarely object-name might contain asterisks andinternal identifiers, such as ****0010.****0002,if Db2 cannot obtain the object name.

object-idThe internal DBID and PSID identifiers, for use byIBM Support.

Reasons that the object remains in the specified statusinclude the following examples:

• Db2 attempted several times but failed toautomatically recover the objects, and this memberstopped trying automatic recovery


• Db2 does not recovery objects in GRECP status incertain conditions, such as the following examples:

– ACCESS(MAINT) is specified when Db2 is started.– LIGHT is specified when Db2 is started.– The objects in GRECP status use a buffer pool that

has the AUTOREC=NO attribute.– The objects in GRECP status are deferred by the

value of the RESTART or DEFER field on panelDSNTIPS.

System actionThe table space or index space that is in the indicatedstatus is not accessible.

User responseWhen this message is issued, no membersubsequently attempts any automatic recovery of theobject. You must recover the objects manually.


Related conceptsNormal restart and recovery (Db2Administration Guide)Related referenceGroup buffer pool RECOVER-pending status(Db2 Utilities)Data sharing status descriptions (Db2 DataSharing Planning and Administration)DSNTIPS: Databases and spaces to startautomatically panel (Db2 Installation andMigration)RESTART OR DEFER field (RESTART subsystemparameter) (Db2 Installation and Migration)START NAMES field (ALL subsystem parameter)(Db2 Installation and Migration)

DSNB330I csect-name GROUP BUFFER POOLgbpname CANNOT BE CONNECTEDFOR REBUILD DB2 REASON CODE= reason1 MVS IXLCONN REASONCODE = reason2

ExplanationDb2 was not able to connect to the named groupbuffer pool for rebuild. reason1 is the Db2 reasoncode. reason2 is the MVS IXLCONN reason code. Seez/OS MVS Programming: Sysplex Services Reference foran explanation of MVS IXLxxxx reason codes.

System actionDb2 stops the rebuild.

Problem determinationIf the MVS IXLCONN reason code is xxxx0C08(structure allocation failed because there was nosuitable facility to allocate based on the preference listin the MVS CFRM administrative policy), or if the MVSIXLCONN reason code is xxxx084C (user does nothave proper Security Access Facility (SAF)authorization), then IFCID 0250, if active, containsadditional diagnostic information.

DSNB331I csect-name REBUILD STARTEDFOR GROUP BUFFER POOLgbpname REASON = reason

ExplanationA rebuild has been initiated for the named group bufferpool. reason indicates the reason why the rebuild wasinitiated. reason can be one of the following:OPERATOR

The operator initiated a SETXCF command toinitiate the rebuild.

LOSSCONNMVS detected a loss of connectivity to the groupbuffer pool.

This message is issued by each Db2 memberparticipating in the rebuild.

System actionThe Db2 members that are actively connected to thenamed group buffer pool participate in the rebuild.Db2 accomplishes the group buffer pool rebuildprocessing in two phases:

1. Quiesce phase. Each member quiesces all localaccess to the group buffer pool.

2. Connect phase. Each member connects to the newstructure. Each page set or partition castout ownerthat has connectivity to original structure isresponsible for writing pages from the originalstructure to the new one. If there are not enoughdata entries in the new structure, the page set andpartition owners cast those pages out to DASDinstead. Each member issues message DSNB332Iafter it completes this activity. After all membershave completed their castout owner rebuild work,the group buffer pool structure owner does the finalsweep and checks to see if there are any changedpages still remaining in the original structure. If so,the structure owner reads the changed pages fromthe original structure and writes them to the new






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_dsharingstatusdescs.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntips.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_restart.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_restart.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_all.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_all.html

one. The structure owner issues messageDSNB333I after it has completed the final sweep.

After all members have responded to MVS indicatingthat its connect phase processing is complete, MVSthen notifies each member that the rebuild iscomplete. Each Db2 member issues messageDSNB338I indicating that the rebuild has completedsuccessfully.

If an error occurs during the rebuild, the rebuild isstopped. Each Db2 member issues messageDSNB335I indicating the reason why the rebuild isstopping, followed by message DSNB339I indicatingthat the rebuild has not completed successfully. Theoperator can also stop rebuilds using the MVS SETXCFcommand.

DSNB332I csect-name THIS MEMBER HASCOMPLETED CASTOUT OWNERWORK FOR GROUP BUFFER POOLgbpname PAGES CAST OUT FROMORIGINAL STRUCTURE = value1PAGES WRITTEN TO NEWSTRUCTURE = value2

ExplanationThis Db2 member has completed its part of the rebuildprocessing for the named group buffer pool for thepage sets and partitions for which it is the castoutowner.

value1 indicates the number of pages that thismember has castout to DASD for the rebuild. If thenew structure has a sufficient number of data entries,then value1 should normally be zero because Db2writes the changed pages from the original structure tothe new structure. However, if the new structure doesnot have sufficient space, then value1 could be greaterthan zero because Db2 responds to insufficient spacein the new structure by casting the changed pages inthe original structure to DASD instead of writing themto the new structure.

value2 indicates how many changed pages thismember wrote to the new structure from the originalas part of the rebuild process. If the new structure hassufficient space, then each Db2 that has connectivityto the original structure writes the changed pages forpage sets and partitions for which it is the castoutowner from the original structure to the new structure,and value2 indicates the number of pages that the Db2member wrote.

value1 and value2 would be zero if this member has nopage set or partition castout ownership responsibility.

This message is issued by each Db2 member that hasconnectivity to the original group buffer pool, and it is

always be preceded by message DSNB331I orDSNB740I.

System actionIf this Db2 member is not the group buffer poolstructure owner, then its rebuild work is done, and itnotifies MVS that it has completed its part of therebuild and awaits later notification that all membershave completed. If this member is the structure owner,then it proceeds to its final sweep processing (seeDSNB333I).

Refer to "System Action" for message DSNB331I foran explanation of the group buffer pool rebuildprocessing.

DSNB333I csect-name FINAL SWEEPCOMPLETED FOR GROUP BUFFERPOOL gbpname PAGES WRITTENTO NEW STRUCTURE = value1

ExplanationDb2 has completed the final sweep for the rebuild ofthe named group buffer pool. A final sweep means thatthe Db2 member that is the group buffer poolstructure owner ensures that all changed pages haveeither been cast out to DASD or have been written tothe new structure after all the page set and partitionowners have finished their work. If any changed pagesare found in the original structure during the finalsweep, then the structure owner writes them out tothe new structure. value1 should be zero in most casesfor a manual rebuild. value1 will probably be greaterthan zero in most cases where the rebuild was initiatedbecause a Db2 lost connectivity to the group bufferpool.

This message is issued by the structure owner and isalways preceded by message DSNB332I.

System actionImmediately after issuing this message, the structureowner notifies MVS that the rebuild has completed,and MVS should soon begin notifying eachparticipating member that the rebuild is complete.

Refer to "System Action" for message DSNB331I foran explanation of the group buffer pool rebuildprocessing.

DSNB335I csect-name REBUILD STOPPEDFOR GROUP BUFFER POOLgbpname REASON = reason1 DB2REASON CODE = reason2


ExplanationA rebuild has been stopped for the named group bufferpool.

reason1 indicates why the rebuild was stopped:OPERATOR

The operator initiated an MVS SETXCF command tostop the rebuild.

LOSSCONNNEWOne or more of the Db2 members lost connectivityto the new group buffer pool structure while therebuild was in progress.

LOSSCONNOLDOne or more of the Db2 members lost connectivityto the original group buffer pool structure while therebuild was in progress.

STRFAILNEWThe new group buffer pool structure failed whilethe rebuild was in progress.

STRFAILOLDThe original group buffer pool structure failedwhile the rebuild was in progress.

DB2REASONDb2 decided to stop the rebuild. The reason codegiven in reason2 indicates why Db2 stopped therebuild.

INSUFFCONNNew structure does not provide connectivity that isbetter than or equivalent to the current structure.

NOBETRCONNNew structure does not provide better connectivitythan the current structure for a LossConn rebuild

If reason1 indicates 'DB2REASON', then reason2specifies a Db2 reason code that indicates why Db2stopped the rebuild. If reason1 is not 'DB2REASON',then reason2 is zero.

This message is normally preceded by messageDSNB331I, which indicates that the rebuild wasstarted and the reason why the rebuild was started.This message is issued by each Db2 memberparticipating in the rebuild. This message is followedby message DSNB339I.

System actionThe new structure is discarded. If the originalstructure is still usable, then all members that stillhave connectivity to the original structure resumeusing it. Members that do not have connectivity to theoriginal structure disconnect, and their connectionsbecome failed-persistent.

If the original structure is not usable, then Db2initiates damage assessment processing for the groupbuffer pool.

System programmer responseIf the rebuild stopped because of "DB2REASON", seethe explanation for the reason code given.

DSNB338I csect-name THE REBUILD FORGROUP BUFFER POOL gbpnameHAS COMPLETED SUCCESSFULLY

ExplanationThe rebuild for the named group buffer pool hassuccessfully completed.

This message is preceded by message DSNB331Iwhich indicates the reason why the rebuild wasstarted. This message is issued by each Db2 memberparticipating in the rebuild.

System actionThe original structure is discarded and all DB2s thatare connected to the group buffer pool begin using thenew structure.

DSNB339I csect-name THE STOP OF THEREBUILD FOR GROUP BUFFERPOOL gbpname HAS COMPLETED

ExplanationThe stop of the rebuild for the named group bufferpool has completed.

This message is preceded by message DSNB335Iwhich indicates the reason why the rebuild wasstopped. This message is issued by each Db2 memberparticipating in the rebuild.

System actionThe new structure is discarded. If the originalstructure is still usable, then all members that stillhave connectivity to the original structure resumeusing it, and members that do not have connectivity tothe original structure disconnect and their connectiongoes into a failed-persistent state.

If the original structure is not usable, then Db2initiates damage assessment processing for the groupbuffer pool.

DSNB340I csect-name UNEXPECTED ERRORDURING REBUILD FOR GROUPBUFFER POOL gbpname MVSservice-name RETURN CODE = rc


MVS service-name REASON CODE= reason

ExplanationDb2 received an unexpected error from MVS duringrebuild processing for the named group buffer pool.

service-name is one of the following:

• IXLREBLD• IXLEERSP

rc is the return code from the MVS service and reasonis the reason code.

System actionDb2 stops the rebuild.

System programmer responseSee z/OS MVS Programming: Sysplex ServicesReference for an explanation of the return and reasoncode for the named MVS service.

DSNB350I csect-name DBNAME database-name SPACENAME space-nameINSTANCE instance-numberCANNOT BE AUTOMATICALLYRECOVERED. DB2 REASON CODE =reason-code

ExplanationFollowing a group buffer pool failure, Db2 cannotautomatically recover the named table space or indexspace.






System actionThe table space or index space remains in group bufferpool recovery pending (GRECP) status and isinaccessible.

User responseUse the START DATABASE command on the tablespace or index space to remove the GRECP status andmake the data accessible. You can also use theRECOVER or LOAD utility with the REPLACE option toclear the GRECP status.

Severity4 (warning)


DSNB351I csect-name DBNAME database-name SPACENAME space-nameINSTANCE instance-numberPARTITION partition-numberCANNOT BE AUTOMATICALLYRECOVERED. DB2 REASON CODE =reason-code

ExplanationFollowing a group buffer pool failure, Db2 cannotautomatically recover the named table space or indexspace partition.















System actionThe partition remains in group buffer pool recoverypending (GRECP) status and is inaccessible.

User responseUse the START DATABASE command on the partitionto remove the GRECP status and make the dataaccessible. You can also use the RECOVER or LOADutility with the REPLACE option to clear the GRECPstatus.

Severity4 (warning)


DSNB352I csect-name AUTOMATICRECOVERY CANNOT BE INITIATEDFOR GROUPBUFFER POOL gbp-name REASON = reason

ExplanationFollowing a failure of the named group buffer pool,Db2 is not able to initiate automatic recovery.

reason indicates the reason why automatic recoverywas not initiated:AUTORECNO

The AUTOREC option is set to NO for the groupbuffer pool.

CONNRELEASEAt least one actively connected Db2 member is notat the proper release to support automaticrecovery.

System actionThe page sets and partitions that are in group bufferpool recovery pending (GRECP) status remaininaccessible.

User responseUse the Db2 -START DATABASE command on the pagesets and partitions to remove the GRECP status andmake the data accessible. You can also use theRECOVERor LOAD utility with the REPLACE option toclear the GRECP status.

If reason is AUTORECNO and you want to enableautomatic recovery for the group buffer pool, use theALTER GROUPBUFFERPOOL command to setAUTOREC to YES for the group buffer pool.

If reason is CONNRELEASE, then you must ensure thatall Db2 members in the group are running at theappropriate release. Automatic recovery is notsupported unless all members are running Version 5 ora later release.

Severity4 (warning)

Related reference-START DATABASE (Db2) (Db2 Commands)-ALTER GROUPBUFFERPOOL (Db2) (Db2Commands)LOAD (Db2 Utilities)RECOVER (Db2 Utilities)Group buffer pool RECOVER-pending status(Db2 Utilities)Data sharing status descriptions (Db2 DataSharing Planning and Administration)

DSNB353I csect-name ASYNCHRONOUSGRECP RECOVERY IN PROGRESSFOR GROUP BUFFER POOLbpoolname

ExplanationFollowing a group buffer pool failure, Db2 triggers anautomatic recovery process to attempt to recoverGRECP page sets for the specified group buffer pool.This message is issued once by any Db2 member whois the page set castout owner on one of the objectsbeing recovered.

System actionCheck for the DSNB354I message to verify thecompletion of the automatic recovery process.

DSNB354I csect-name ASYNCHRONOUSGRECP RECOVERY HASCOMPLETED FOR GROUP BUFFERPOOL bpoolname.

ExplanationDb2 has completed the GRECP recovery process forthose GRECP page sets in the group buffer poolspecified in the message. This message is issued onceby any Db2 member who previously issued aDSNB353I message, who is the page set castoutowner on one of the objects being recovered.








https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_altergroupbufferpool.html








DSNB355I csect-name GROUP BUFFER POOLgbpname RECOVERY LRSN VALUESMIGHT CAUSE A DELAY IN GRECPRECOVERY. PAGE LEVEL =minimum-page-lrsn MEMBERLEVEL = minimum-member-lrsnPAGE LEVEL IN LOCAL TIMESTAMP= minimum-page-timestampMEMBER LEVEL IN LOCALTIMESTAMP = minimum-member-timestamp

ExplanationThis message is issued at a group buffer poolcheckpoint, if the minimum page LRSN or theminimum member LRSN that are used in recoveryfrom the group buffer pool recovery pending (GRECP)state meet either of the following conditions:

• The minimum page LRSN is older than the time whenthe third-to-last group buffer pool checkpoint wastaken.

For example, suppose that group buffer poolcheckpoints are taken at times T1, T2, T3, and T4. Attime T4, if Db2 detects that the time of the minimumpage LRSN is earlier than time T1, this message isissued.

• The minimum member LRSN is invalid. The value isX'FFFFFFFFFFFF' for a six-byte LRSN, orX'FFFFFFFFFFFFFFFFFFFF' for a ten-byte LRSN.

minimum-page-lrsnThe minimum page LRSN. This value is the oldestchanged page clean-to-dirty LRSN that wasrecorded at the time of the last group buffer poolcheckpoint.

minimum-member-lrsnThe minimum member LRSN. This value is theminimum member-level, write-pending LRSN thatwas recorded at the last group buffer poolcheckpoint. Db2 records a restart/redo LRSN foreach member of the data sharing group at a groupbuffer pool checkpoint. The minimum memberLRSN reflects the minimum value across allmembers. If the group buffer pool fails, Db2 does amerge log scan to recover the page sets andpartitions that are in GRECP status. Db2 uses eachmember’s restart/redo LRSN in conjunction withthe minimum page LRSN to determine the startingpoint for the merge log scan.

minimum-page-timestampThe local timestamp of the minimum page-levelLRSN.

minimum-member-timestampThe local timestamp of the minimum member-level LRSN. If the minimum member-level LRSN isinvalid, the string ********** is displayed.

The local timestamps are in the following format:

hh:mm:ss month dd, yyyy

hh:mm:ssThe time portion of the timestamp, expressed ashours, minutes, and seconds.

monthAn alphanumeric abbreviation for the month.Possible values are:

Month month value in the localtimestamp

January JAN

February FEB

March MAR

April APR

May MAY

June JUN

July JUL

August AUG

September SEP

October OCT

November NOV

December DEC

ddThe day of the month.

yyyyThe year.

System actionProcessing continues. This message is displayed onthe console until either of the following situationsoccurs:

• The minimum page LRSN is newer than the third-to-last group buffer pool checkpoint, and the minimummember LRSN is valid.

• The member that issued the message disconnectsfrom the group buffer pool.


User responseIf this message is displayed after all Db2 data sharingmembers are running normally or have shut downnormally, contact IBM Support for assistance.

If this message is displayed after some Db2 datasharing members shut down abnormally, restart thoseDb2 members.

While the condition that caused this message persists,applications can continue to run without any impact.However, this condition lengthens the time that isrequired for recovery from GRECP status.

This message is issued intermittently when thecondition that causes it occurs. If DSNB355Imessages continue to be displayed, contact IBMSupport for assistance.


• Dump of the group buffer pool.• Console output from the system on which the job

was run, and a listing of the SYSLOG data set for theperiod of time that spans the failure.

DSNB356I csect-name FOR GROUP BUFFERPOOL gbp-name , THE CONDITIONTHAT CAUSED THE PREVIOUSDSNB355I MESSAGE DOES NOTCURRENTLY EXIST. PREVIOUSPAGE LEVEL = previous-page-lrsnprevious-page-timestampCURRENT PAGE LEVEL = current-page-lrsn current-page-timestampPREVIOUS MEMBER LEVEL =previous-member-lrsn previous-member-timestamp CURRENTMEMBER LEVEL = current-member-lrsn current-member-timestamp

ExplanationThis message is issued at a group buffer poolcheckpoint when the minimum page LRSN is newerthan the third-to-last group buffer pool checkpoint,and the minimum member LRSN is valid.



previous-page-lrsnThe page-level LRSN in the previous DSNB355Imessage.

previous-page-timestampThe local timestamp of the page-level LRSN in theprevious DSNB355I message.

current-page-lrsnThe current page-level LRSN.

current-page-timestampThe local timestamp of the current page-levelLRSN.

previous-member-lrsnThe member-level LRSN in the previous DSNB355Imessage.

previous-member-timestampThe local timestamp of the member-level LRSN inthe previous DSNB355I message.

current-member-lrsnThe current member-level LRSN.

current-member-timestampThe local timestamp of the current member-levelLRSN.






January JAN

February FEB

March MAR

April APR

May MAY

June JUN

July JUL

August AUG

September SEP

October OCT

November NOV

December DEC


yyyyThe year.

System action:Db2 processing continues.


Related informationDSNB355Icsect-name GROUP BUFFER POOL gbpnameRECOVERY LRSN VALUES MIGHT CAUSE ADELAY IN GRECP RECOVERY. PAGE LEVEL =minimum-page-lrsn MEMBER LEVEL =minimum-member-lrsn PAGE LEVEL IN LOCALTIMESTAMP = minimum-page-timestampMEMBER LEVEL IN LOCAL TIMESTAMP =minimum-member-timestamp

DSNB357I csect-name AUTOMATIC LPLRECOVERY SUPPRESSED FOROBJECT TYPE object-type OBJECTNAME object-name REASONreason-type

ExplanationOne or more pages in the object that is identified in themessage have been added to the logical page list(LPL). However, Db2 cannot initiate automatic LPLrecovery due to an environmental condition thatprevents automatic LPL recovery.

The object could be a table space, an index space, or apartition within a table space or an index space that isidentified by the object-type. object-name identifiesthe name.

If the object is a table space or an index space, theformat of the name is dbname.spacename. If theobject is a partition within a table space or an indexspace, the format of the name isdbname.spacename.partnumber. dbname is thedatabase name. spacename is the table space or theindex space name. partnumber is the partition number.

reason indicates the condition that prevents Db2 frombeing able to initiate automatic LPL recovery. Here is alist of the potential values for reason:DASD

Db2 encountered a DASD I/O error.RESTART

Db2 is in Restart or End_Restart mode.GBP

Db2 Group Buffer Pool structure failure or 100%loss of connectivity.

System actionThe Automatic LPL Recovery is not initiated.

Programmer responseCheck the reason that is specified to solve the systemcondition. To recover the LPL page, perform one of thefollowing actions:

• Issue the START DATABASE command with theSPACENAM option

• Run the RECOVER or LOAD utility with REPLACEkeyword.

DSNB401I BUFFERPOOL NAME bp-name,BUFFERPOOL ID bp-id, USECOUNT use-count

ExplanationThis message displays output from the DISPLAYBUFFERPOOL command. For each buffer pool, thismessage marks the beginning of multiple lines ofinformation about that buffer pool. Some lines in theoutput have their own message numbers oralphanumeric identifiers to assist with identification.

The first line (DSNB401I) contains the followinginformation:

bp-nameThe external name of the buffer pool. bp-name canbe one of the following values: BP0 to BP49,BP8K0 to BP8K9, BP16K0 to BP16K9, BP32K, orBP32K1 to BP32K9.

bp-idThe internal identifier for the buffer pool. bp-id canbe one of the following values: 0 to 49, 80 to 89,100 to 109, or 120 to 129.

use-countThe number of open table spaces or index spacesthat use this buffer pool. A value of zero meansthat the buffer pool is inactive.

The remaining output for each buffer pool consists ofone or more of the following sections, in the indicatedorder:

• DSNB402I: Information about allocation status• DSNB404I: Threshold information• DSNB406I: PGFIX and PGSTEAL information• DSNB409I: Start time of the statistics interval for

DETAIL(INTERVAL)• DSNB410I: Start time of the statistics interval for

DETAIL(*)• DSNB411I: Page read statistics• DSNB412I: Sequential prefetch statistics• DSNB413I: List prefetch statistics• DSNB414I: Dynamic prefetch statistics• DSNB415I: Prefetch statistics• DSNB420I: Page write statistics• DSNB421I: Page-write threshold statistics• DSNB431I: Information about allocation status for

simulated buffer pools


• DSNB432I: Simulated buffer pool activity• DSNB440I: Parallel activity statistics• DSNB441I: LPL activity statistics• DSNB453I: Cached and changed page statistics• DSNB455I: Synchronous I/O delay statistics• DSNB456I: Asynchronous I/O delay statistics• DSNB457I: Simulated buffer pool page statistics• DSNB460I: Page set and partition list information

(for a data-sharing environment)• DSNB464I: Page set and partition list information

(for a non-data-sharing environment)• DSNB466I: Page set and partition statistics• DSNB467I: Data set statistics• DSNB546I: Frame size allocation

If information cannot be reported, one or more of thefollowing messages is returned:

• DSNB408I: No detail statistics available• DSNB459I: Open failure for a data set• DSNB463I: No objects matched selection criteria

The DISPLAY BUFFERPOOL output ends with one ofthe following messages:

• DSN9022I: Normal completion• DSNB499I: Display terminated because ofinsufficient space

DSNB402I: Information about allocationstatusThe basic buffer pool information is followed by adescription of the allocation status of the buffer pool.

The values of VPSIZE MINIMUM and VPSIZEMAXIMUM are used only when AUTOSIZE =YES.

DSNB402I - BUFFER POOL SIZE = pool-size BUFFERS AUTOSIZE = autosize VPSIZE MINIMUM = minimum size VPSIZE MAXIMUM = maximum-size ALLOCATED = allocated-buffers TO BE DELETED = delete-buffers IN-USE/UPDATED = current-buffers

BUFFER POOL SIZE = pool-size BUFFERSThe user-specified buffer pool size.

AUTOSIZE = autosizeThe buffer pool AUTOSIZE attribute that isapplicable to the current allocation of the bufferpool.YES

The buffer pool uses Workload Manager (WLM)services, if available, to automatically adjustthe size of the buffer pool. The size is adjustedbased on dynamic monitoring of the workload

goals and the storage that is available on thesystem.

NOThe buffer pool does not use WLM services forautomatic sizing adjustment of buffer pools.

VPSIZE MINIMUM = minimum sizeThe minimum size of the buffer pool. This value ismeaningful only when the value of autosize is YES.If the value was never specified, a value of 0 isshown, and Db2 uses a default value of 75% of thespecified value of VPSIZE.

VPSIZE MAXIMUM = maximum-sizeThe maximum size of the buffer pool. This value ismeaningful only when the value of autosize is YES.If the value was never specified, a value of 0 isshown, and Db2 uses the defaults value, which is25% greater than the specified VPSIZE value.

ALLOCATED = allocated-buffersThe number of allocated buffers in an active bufferpool.

TO BE DELETED = delete-buffersThe number of buffers to be deleted in an activebuffer pool because of pool contraction.

IN-USE/UPDATED = current-buffersThe number of currently active buffers in the bufferpool. These buffers cannot be stolen.

DSNB404I: Threshold informationThe information about allocation status is followed byinformation about the user-modifiable thresholds forthe buffer pool.

DSNB404I - THRESHOLDS - VP SEQUENTIAL = vpseq SP SEQUENTIAL = spseq DEFERRED WRITE = dwt VERTICAL DEFERRED WRT = dwv1,dwv2 PARALLEL SEQUENTIAL = vppseqt ASSISTING PARALLEL SEQT = vpxpseqt

vpseqThe sequential steal threshold for the virtual pool,expressed as a percentage of the total buffer poolsize.

spseqThe sequential steal threshold for the simulatedpool, expressed as a percentage of the totalsimulated buffer pool size.

dwtThe free-buffer deferred write threshold for thebuffer pool, expressed as a percentage of the totalbuffer pool size.


dwv1The vertical deferred write threshold for the bufferpool, expressed as a percentage of the total bufferpool size.

dwv2The vertical deferred write threshold for the bufferpool, expressed as an absolute number of buffers.dwv2 is used to determine the threshold only ifdwv1 is 0 and dwv2 is non-zero. Otherwise, dwv1is used to determine the threshold.

vppseqtThe sequential threshold for parallel queryprocessing, expressed as a percentage of thevirtual sequential steal threshold. When thethreshold is set to 0, parallel query processing isnot supported.

vpxpseqtThe assisting parallel sequential threshold,expressed as a percentage of the sequentialthreshold for parallel query processing. Use thevpxpseqt value to control how much bufferresource is used when this Db2 member isassisting another member of the group in parallelprocessing. When the threshold is set to 0, thisbuffer pool is not used to assist other data-sharingmembers in processing a query. In a non-data-sharing environment, this value is ignored.

DSNB406I: PGFIX and PGSTEALinformationThe DISPLAY BUFFERPOOL output includes adescription of the PGFIX and PGSTEAL attributes forthe buffer pool.

CURRENT = current-pgfixThe value of the page fix (PGFIX) attribute for thecurrent allocation of the buffer pool.YES

The buffer pool is fixed in real storage for thelong term.

NOThe buffer pool is fixed in real storage onlyduring an I/O operation.

PENDING = pending-pgfixThe value of the PGFIX attribute that is to beapplied for the next allocation of the virtual bufferpool.YES

The buffer pool is to be fixed in real storage forthe long term.

NOThe buffer pool is to be fixed in real storageonly during an I/O operation.

PAGE STEALING METHOD = current-pgstealThe page stealing method (PGSTEAL) that is in usefor the buffer pool.LRU

The least recently used (LRU) algorithm is usedto manage page stealing. This method is thedefault value.

FIFOThe first-in, first-out (FIFO) algorithm is usedto manage page stealing.

NONENo page stealing occurs. Objects that use thisbuffer pool are kept resident.

Related information:

Fixing a buffer pool in real storage (Db2Performance)Choosing a page-stealing algorithm (Db2Performance)

DSNB408I: No detail statistics availableDSNB408I indicates that, although you specified theDETAIL option on the DISPLAY BUFFERPOOLcommand, no detail statistics are available for therequested buffer pool. The statistics are not availablebecause the pool has not been activated since Db2started.

BUFFER POOL bp-nameThe name of the buffer pool.

DSNB409I: Start time of the statisticsinterval for DETAIL(INTERVAL)When you specify the DETAIL(INTERVAL) option, theoutput includes the start time of the interval for whichthe statistics were accumulated.

DSNB409I - INCREMENTAL STATISTICS SINCE base-time

base-timeThe start time. This value is either the time of theprevious incremental display or, if no previousincremental display exists, the time that the bufferpool was first activated.

The format is hh:mm:ss month dd, yyyy

hh:mm:ssThe time expressed as hour:minutes:seconds.

monthAn alphanumeric abbreviation for the month.For example, a value of OCT means October.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_longtermpagefix4bufferpools.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_choosepagesteal.html


yyyyThe year.

DSNB410I: Start time of the statisticsinterval for DETAIL(*)When you specify the DETAIL(*) option, the outputincludes the start time of the interval for which thestatistics were accumulated.

DSNB410I - CUMULATIVE STATISTICS SINCE base-time

base-timeThe start time. This value is the time the bufferpool was first activated.

The format is hh:mm:ss month dd, yyyy

hh:mm:ssThe time expressed as hour:minutes:seconds.

monthAn alphanumeric abbreviation for the month.For example, a value of OCT means October.


yyyyThe year.

DSNB411I: Page read statisticsWhen you specify the DETAIL option, the outputincludes the page read statistics for the buffer pool.

DSNB411I - RANDOM GETPAGE = rgp SYNC READ I/O (R) = srr SEQ. GETPAGE = sgp SYNC READ I/O (S) = srs SYNC READ I/O (ZHL) = srrz DMTH HIT = dmt PAGE-INS REQ = pir SEQUENTIAL = seq VPSEQT HIT = vsh RECLASSIFY = rcy

RANDOM GETPAGE = rgpThe number of nonsequential GETPAGE requests.

SYNC READ I/O (R) = srrThe number of synchronous read I/O operationsfor nonsequential GETPAGE requests.

SYNC READ I/O (ZHL) = srrzThe number of synchronous read I/O operationsusing zHyperLink.

SEQ. GETPAGE = sgpThe number of sequential GETPAGE requests.

SYNC READ I/O (S) = srsThe number of synchronous read I/O operationsfor sequential GETPAGE requests.

DMTH HIT = dmtThe number of times that the data managementthreshold was reached.

PAGE-INS REQ = pirThe number of page-in operations that arerequired for read I/O.

SEQUENTIAL = seqThe number of buffers on the sequential least-recently-used (SLRU) chain.

VPSEQT HIT = vshThe number of times that the size of the SLRUchain reached the sequential steal threshold (theVPSEQT value) for the buffer pool.

RECLASSIFY = rcyA statistic that is used by IBM for serviceability.


Buffer pool thresholds that you can change (Db2Performance)-ALTER BUFFERPOOL (Db2) (Db2 Commands)

DSNB412I: Sequential prefetch statisticsWhen you specify the DETAIL option, the outputincludes the sequential prefetch statistics for thebuffer pool.

REQUESTS = pftThe number of times that sequential prefetch wasrequested.

PREFETCH I/O = pioThe number of sequential prefetch read I/Ooperations.

PAGES READ = pfpThe number of pages that are read because ofsequential prefetch.


Sequential prefetch (PREFETCH='S') (Db2Performance)

DSNB413I: List prefetch statisticsWhen you specify the DETAIL option, the outputincludes the list prefetch statistics for the buffer pool.

DSNB413I - LIST PREFETCH - REQUESTS = pft PREFETCH I/O = pio PAGES READ = pfp

REQUESTS = pftThe number of times that list prefetch wasrequested.

PREFETCH I/O = pioThe number of list prefetch read I/O operations.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_bufferpoolthresholds2change.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_alterbufferpool.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_sprefetch.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_sprefetch.html

PAGES READ = pfpThe number of pages that are read because of listprefetch.


List prefetch (PREFETCH='L' or 'U') (Db2Performance)

DSNB414I: Dynamic prefetch statisticsWhen you specify the DETAIL option, the outputincludes the dynamic prefetch statistics for the bufferpool.

DSNB414I - DYNAMIC PREFETCH - REQUESTS = pft PREFETCH I/O = pio PAGES READ = pfp

REQUESTS = pftThe number of times that dynamic prefetch wasrequested.

PREFETCH I/O = pioThe number of dynamic prefetch read I/Ooperations.

PAGES READ = pfpThe number of pages that are read because ofdynamic prefetch.


Dynamic prefetch (PREFETCH='D') (Db2Performance)

DSNB415I: Prefetch statisticsWhen you specify the DETAIL option, the outputincludes the prefetch statistics for the buffer pool.

DSNB415I - PREFETCH DISABLED - NO BUFFER = pfd NO READ ENGINE = ree

NO BUFFER = pfdThe number of times that prefetch was disabledfor one of the following reasons:

• The buffer pool reached the prefetch disabledthreshold (90% full).

• A user disabled prefetch by setting the VPSEQTthreshold for the buffer pool to zero.

NO READ ENGINE = reeThe number of times that prefetch was disabledbecause an asynchronous read processor was notavailable.


Read operations and prefetch I/O (Db2Performance)

DSNB420I: Page write statisticsWhen you specify the DETAIL option, the outputincludes the page write statistics for the buffer pool.

SYS PAGE UPDATES = pages-updatedThe number of buffer updates.

SYS PAGES WRITTEN = pages-writtenThe number of pages that are written to disk.

ASYNC WRITE I/O = async-writesThe number of asynchronous write I/O operations.

SYNC WRITE I/O = sync-writesThe number of synchronous write I/O operations.

PAGE-INS REQ = page-insThe number of page-ins that are required for writeI/O.

DSNB421I: Page-write threshold statisticsWhen you specify the DETAIL option, the outputincludes the page-write threshold statistics for thebuffer pool.

DSNB421I - DWT HIT = dwt VERTICAL DWT HIT = vdw

DWT HIT = dwtThe number of times that the deferred writethreshold was reached.

VERTICAL DWT HIT = vdwThe number of times that the vertical deferredwrite threshold was reached.


Buffer pool thresholds that you can change (Db2Performance)

DSNB431I: Information about allocationstatus for simulated buffer poolsThe description of the allocation status of the bufferpool is followed by a description of the allocationstatus of the simulated buffer pool.

DSNB431I - SIMULATED BUFFER POOL SIZE = pool-size BUFFERS ALLOCATED = allocated-buffers IN-USE = current-in-use HIGH-IN-USE = high-in-use SEQ-IN-USE = current-sequential-in-use HIGH SEQ-IN-USE = high-sequential-in-use

SIMULATED BUFFER POOL SIZE = pool-sizeBUFFERS

The user-specified simulated buffer pool size.ALLOCATED = allocated-buffers

The number of simulated buffers that are currentlyallocated in the simulated buffer pool.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_lprefetch.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_lprefetch.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_dprefetch.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_dprefetch.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_readoperation.html




IN-USE = current-in-useThe number of simulated buffers that are currentlybeing used to track pages.

HIGH IN-USE = high-in-useThe highest number of simulated buffers that havebeen in use in the simulated buffer pool since thebuffer pool simulation began.

SEQ IN-USE = current-sequential-in-useThe number of simulated buffers for sequentiallyaccessed pages that are currently in use in thesimulated buffer pool.

HIGH SEQ-IN-USE = high-sequential-in-useThe highest number of simulated buffers forsequentially accessed pages that have been in usein the simulated buffer pool since the buffer poolsimulation began.

DSNB432I: Simulated buffer pool activityWhen you specify the DETAIL option, the outputincludes statistics on activity in the simulated bufferpool, including the numbers of page accesses that thebuffer pool simulation determined could be avoided,for various types of read activity.

DSNB432I - SIMULATED BUFFER POOL ACTIVITY - AVOIDABLE READ PAGE MISSES - SYNC FROM DASD (R) = pages-sync-rand-dasd SYNC FROM DASD (S) = pages-sync-seq-dasd ASYNC FROM DASD = pages-async-dasd SYNC FROM GBP (R) = pages-sync-rand-gbp SYNC FROM GBP (S) = pages-sync-seq-gbp ASYNC FROM GBP = pages-async-gbp PAGES MOVED INTO SIMULATED BUFFER POOL = pages-to-sim-bp TOTAL AVOIDABLE SYNC I/O DELAY = sync-io-delay MILLISECONDS

pages-sync-rand-dasdThe number of pages accessed randomly byavoidable synchronous read I/O from disk.

pages-sync-seq-dasdThe number of pages accessed sequentially byavoidable synchronous read I/O from disk.

pages-async-dasdThe number of pages prefetched by avoidableasynchronous read I/O from disk.

pages-sync-rand-gbpThe number of pages accessed randomly byavoidable synchronous read from the group bufferpool..

pages-sync-seq-gbpThe number of pages accessed sequentially byavoidable synchronous read from the group bufferpool.

pages-async-gbpThe number of pages accessed by avoidableasynchronous read from the group buffer pool.

pages-to-sim-bpThe number of pages that were logically movedfrom the virtual buffer pool into the simulatedbuffer pool.

sync-io-delayThe total time in milliseconds that the buffer poolsimulation determined would be spent waiting forsynchronous read I/O from disk.

DSNB440I: Parallel activity statisticsWhen you specify the DETAIL option, the outputincludes statistics about parallel activities for thebuffer pool.

DSNB440I - PARALLEL ACTIVITY - PARALLEL REQUEST = tpa DEGRADED PARALLEL = dpa

PARALLEL REQUEST = tpaThe total number of negotiations with the bufferpool for the requested number of sequentialprefetch streams.

DEGRADED PARALLEL = dpaThe total number of times that the negotiationresulted in the degraded mode of paralleloperations.

DSNB441I: LPL activity statisticsWhen you specify the DETAIL option, the outputincludes statistics about LPL activity for the bufferpool.

DSNB441I - LPL ACTIVITY - PAGES ADDED = pages

pagesThe total number of pages for all page sets that areadded to the logical page list (LPL) in this bufferpool. This value is equal to the number ofDSNB250E messages that are written to thesystem log after the most recent execution of theDISPLAY BUFFERPOOL command with the DETAILoption.


“DSNB250E” on page 52Displaying the logical page list (Db2 AdministrationGuide)Characteristics of pages that are in error (Db2Administration Guide)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_displaylogicalpagelist.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_displaylogicalpagelist.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_pageerrorcharacteristics.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_pageerrorcharacteristics.html

DSNB453I: Cached and changed pagestatisticsThe output includes the number of cached pages andchanged pages in the buffer pool for a data set if all ofthe following conditions are true:

• You specified the LSTATS option on the DISPLAYBUFFERPOOL command.

• The buffer pool is an active buffer pool.• The number of cached and changed pages are not

zero.

The relevant table space or index space is identified ineither line DSNB464I or line DSNB465I. The data setis identified in line DSNB466I.

DSNB453I - VP CACHED PAGES - CURRENT = vcount MAX = mvcount CHANGED = ccount MAX = mccount

CURRENT = vcountThe number of cached pages in the virtual pool forthe data set. This value is the number of buffersthat contain pages for the data set in the bufferpool.

MAX = mvcountThe maximum number of cached pages in thevirtual pool for the data set since the last DISPLAYBUFFERPOOL command with the LSTATS optionwas issued.

CHANGED = ccountThe number of changed pages in the virtual poolfor the data set. This value is the number of buffersthat were changed in the buffer pool for the dataset.

MAX = mccountThe maximum number of changed pages in thevirtual pool for the data set since the last DISPLAYBUFFERPOOL command with the LSTATS optionwas issued.

DSNB455I: Synchronous I/O delaystatisticsThe output includes synchronous I/O delay statistics ifall of the following conditions are true:


• The buffer pool is an active buffer pool.• The values of the synchronous I/O delay statistics

are not zero.

These synchronous I/O delay statistics are reportedfor a data set for an open table space or index spacethat is associated with the buffer pool. The values that

are listed are the statistics that were gathered sincethe last display for the data set.

Note: There are two sections to report synchronousI/O delays. The statistics displayed under“SYNCHRONOUS I/O DELAYS” shows I/Os that did notuse zHyperlink.

The relevant table space or index space is identified ineither line DSNB464I or line DSNB465I. The relativedata set within the table space or index space isidentified in line DSNB466I.

DSNB455I - SYNCHRONOUS I/O DELAYS - AVERAGE DELAY = avd MAXIMUM DELAY = mxd TOTAL PAGES = tpg

avdThe average I/O delay in milliseconds for pages inthe data set.

mxdThe maximum I/O delay in milliseconds for pagesin the data set.

tpgThe total number of pages that are read or writtenfor the data set.

SYNCHRONOUS I/O DELAYS WITH ZHYPERLINK - AVERAGE DELAY = avdz MAXIMUM DELAY = mxdz TOTAL PAGES = tpgz

avdzThe average I/O delay in microseconds for pages inthe data set when zHyperLink is used.

mxdzThe maximum I/O delay in microseconds for pagesin the data set when zHyperLink is used.

tpgzThe total number of pages that are read or writtenfor the data set when zHyperLink is used.


Read operations and prefetch I/O (Db2Performance)

DSNB456I: Asynchronous I/O delaystatisticsThe output includes asynchronous I/O delay statisticsif all of the following conditions are true:


• The buffer pool is an active buffer pool.• The values of the asynchronous I/O delay statistics

are not zero.




These asynchronous I/O delay statistics are reportedfor a data set for an open table space or index spacethat is associated with the buffer pool. The values thatare listed are the statistics that were gathered sincethe last display for the data set.

The relevant table space or index space is identified ineither line DSNB464I or line DSNB465I. The relativedata set within the table space or index space isidentified in line DSNB466I.

DSNB456I - ASYNCHRONOUS I/O DELAYS - AVERAGE DELAY = avd MAXIMUM DELAY = mxd TOTAL PAGES = tpg TOTAL I/O COUNT = tio

avdThe average I/O delay in milliseconds for pages inthe data set.

mxdThe maximum I/O delay in milliseconds for pagesin the data set.

tpgThe total number of pages that are read or writtenfor the data set.

tpgThe total number of I/O operations that are issuedfor the data set.

DSNB457I: Simulated buffer pool pagestatisticsThe output includes the number of simulated pages inthe simulated buffer pool for a data set if all of thefollowing conditions are true:


• The buffer pool is an active buffer pool.• The number of simulated pages in the simulated

buffer pool is not zero.

The relevant table space or index space is identified ineither line DSNB464I or line DSNB465I. The data setis identified in line DSNB466I.

DSNB457I - NUMBER OF PAGES IN THE SIMULATED BUFFER POOL - CURRENT = scount MAX = mscount

CURRENT = scountThe number of pages from the data set that arecurrently simulated in the simulated buffer pool.

MAX = mscountThe maximum number of pages from the data setthat have been simulated in the simulated bufferpool since the last DISPLAY BUFFERPOOLcommand with the LSTATS option was issued.

DSNB459I: Open failure for a data setMessage DSNB459I indicates that a previous attemptto access a data set failed because of an allocation oropen error. This message is displayed only when youspecify the LIST option on the DISPLAY BUFFERPOOLcommand for an active buffer pool and this errorcondition occurs.

The relevant table space or index space is identified ineither line DSNB464I or line DSNB465I.

DSNB459I - csect-name OPEN FAILURE HAS OCCURRED FOR DATASET dsn


DATASET = dsnThe data set number. This value is the relative dataset number within a table space or index space.

Other data set and buffer pool information might bedisplayed in subsequent messages.

DSNB460I: Page set and partition listinformation (for a data-sharingenvironment)When you specify the LIST option, the output includesinformation about page sets and partition lists.

The message output begins with the introductory textPAGE SET/PARTITION LIST INFORMATION. Theintroductory text is followed by column headers andmultiple lines of information.

DSNB460I @----------------PAGE SET/PARTITION LIST INFORMATION---------------- --------DATA SHARING INFO-------- TS GBP MEMBER CASTOUT USE P-LOCKDATABASE SPACE NAME INST PART IX DEP NAME OWNER COUNT STATE ======== =========== ==== ==== == === ======== ======= ===== ======

The output contains the following columns, in theindicated order:

DATABASEThe name of the database. This field is blank whenthe line provides information about the samedatabase as the preceding line or lines.

SPACE NAMEThe name of the table space. This field is blankwhen the line provides information about the sametable space as the preceding line or lines.


INSTThe instance number.

PARTOne of the following values:

• The partition number.• For a simple table space or simple index space: a

blank.• For non-partitioned indexes on a partitioned

table space: the logical partition numberpreceded by the character L (for example, L01).

TS IXThe type of object: either TS for table space or IXfor index space.

GBP DEPAn indicator of group buffer pool (GBP)dependency. The indicator can be either of thefollowing values:Y

The page set or partition is GBP-dependent.N

The page set or partition is not GBP-dependent.

MEMBER NAMEThe name of the member that the detail linepertains to.

CASTOUT OWNERAn indicator of whether the member is the castoutowner. The indicator can be either of the followingvalues:Y

The member is the castout owner.Blank

The member is not the castout owner.USE COUNT

The number of active claimers or drainers for thepage set or partition for the member.

P-LOCK STATEThe P-lock state that the member currently holds.The state can be any of the following values:IS

R/O interest. Other members have interest inthis page set or partition. The page set orpartition is GBP-dependent.

IXR/W interest. Other members have interest inthis page set or partition. The page set orpartition is GBP-dependent.

SR/O interest. Other members might be readingthe page set or partition. The page set orpartition is not GBP-dependent.

SIXR/W interest. Other members might be readingthe page set or partition. The page set orpartition is GBP-dependent.

NSUR/W interest. The page set or partition is GBP-dependent.

XR/W interest. No other members are accessingthe page set or partition. The page set orpartition is not GBP-dependent.

USA temporary state that can be held by arestarting Db2 when "waiting for retainedlocks" is enabled.

numberA number for use as a diagnostic aid. A numberis displayed only when a DISPLAYBUFFERPOOL command encounters anundefined lock state.

If the DISPLAY BUFFERPOOL LIST command findsmore than 255 lines of output to display, the output ispresented in multiple sections. Each section is a newinstance of message DSNB460I with the addition of"(CONTINUED)" in the message heading:DSNB460I @ (CONTINUED)

Message DSNB460I is issued in a data-sharingenvironment. In a non-data-sharing environment,message DSNB464I is issued instead.

If no information is available, message DSNB460I isfollowed by message DSNB463I.

DSNB463I: No objects matched selectioncriteriaMessage DSNB463I indicates that Db2 did not find anypage sets or partitions that matched the selectioncriteria.

DSNB463I - * * * NO OBJECTS MATCHED LIST/LSTATS SELECTION CRITERIA

For example, this message is displayed for DISBPOOL(BP0) GBPDEP(Y) if Db2 did not find any pagesets or partitions that are group-buffer-pooldependent (GBP-dependent).

When message DSNB463I is returned, the DISPLAYBUFFERPOOL command terminates normally.

If you expected to see a list of page sets or partitions,review and correct the syntax of the DISPLAYBUFFERPOOL command as needed. Consider addingor changing the filter keywords to obtain a list of pagesets or partitions.


DSNB464I: Page set and partition listinformation (for a non-data-sharingenvironment)When you specify the LIST option, the output includesinformation about page sets and partition lists.

The message output begins with the introductory textPAGE SET/PARTITION LIST INFORMATION. Theintroductory text is followed by column headers andmultiple lines of information.

DSNB464I @PAGE SET/PARTITION LIST INFORMATION TS USE DATABASE SPACE NAME INST PART IX COUNT ======== =========== ==== ==== == =====

DATABASEThe name of the database. This field is blank whenthe line provides information about the samedatabase as the preceding line or lines.

SPACE NAMEThe name of the table space. This field is blankwhen the line provides information about the sametable space as the preceding line or lines.

INSTThe instance number.

PARTOne of the following values:

• The partition number.• For a simple table space or simple index space, a

blank.• For non-partitioned indexes on a partitioned

table space, the logical partition numberpreceded by the character L (for example, L01).

TS IXThe type of object: either TS for table space or IXfor index space.

USE COUNTThe number of active claimers or drainers for thepage set or partition for the member.

If the DISPLAY BUFFERPOOL LIST command findsmore than 255 lines of output to display, the output ispresented in multiple sections. Each section is a newinstance of message DSNB464I with the addition of"(CONTINUED)" in the message heading:DSNB464I @ (CONTINUED)

Message DSNB464I is issued in a non-data-sharingenvironment. In a data-sharing environment, messageDSNB460I is issued instead.

If no information is available, message DSNB464I isfollowed by message DSNB463I.

DSNB466I: Page set and partition statisticsWhen you specify the LSTATS option, the outputincludes statistics for data sets. Those statistics areintroduced by message DSNB466I.

DSNB467I: Data set statisticsWhen you specify the LSTATS option, the outputincludes statistics about data sets for objects that areassociated with active buffer pools.

DSNB467I - STATISTICS FOR object-type database-name.space-name INSTANCE instance-number - DATA SET #: set-number USE COUNT: application-count

STATISTICS FOR object-typeThe type of object: either TABLE SPACE or INDEXSPACE.




DATA SET #: set-numberThe relative data set number within the tablespace or index space.

USE COUNT: application-countThe number of applications that have a claim ordrain on the page set or partition.

This message is followed by one or more of thefollowing messages: DSNB453I, DSNB455I, orDSNB456I.


Claims and drains (Db2 Performance)

DSNB546I: Frame size allocationMessage DSNB546I describes the frame sizeallocation status of the buffer pool. If the specifiednumber of buffers with the specified frame size are notavailable, Db2 allocates some of the buffers with adifferent frame size. In that case, Db2 issues multipleinstances of this message to show the number ofbuffers that are allocated with each frame size.

DSNB546I - PREFERRED FRAME SIZE preferred-size buffer-count BUFFERS USING frame-size FRAME SIZE ALLOCATED

preferred-sizeThe requested frame size. If you used the ALTERBUFFERPOOL command with the FRAMESIZE


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_claimsdrans4concurrency.html

option, the specified FRAMESIZE value isdisplayed as preferred-size.

This value can be 4K, 1M, or 2 GB.

buffer-countThe number of buffers that are allocated with theframe-size value. This value might include storageframes that have been logically removed from thebuffer pool, but which Db2 cannot yet free.

frame-sizeThe actual frame size that Db2 used for thebuffers.

This value can be 4K, 1M, or 2 GB.

DSN9022I: Normal completionThe DISPLAY THREAD output normally ends withmessage DSN9022I.


“DSN9022I” on page 1196

DSNB499I: Display terminated because ofinsufficient spaceIf the DISPLAY BUFFERPOOL output is too long, theoutput ends with message DSNB499I. This messageindicates that the command was unable to obtainstorage for more messages. This situation occurs onlyfor a long display request, such as a detail display formany buffer pools.

The output is truncated.

Reissue the DISPLAY BUFFERPOOL command, andspecify a smaller number of buffer pools.


Related tasksMonitoring buffer pools (Db2 AdministrationGuide)Monitoring and tuning buffer pools by usingonline commands (Db2 Performance)Related reference-DISPLAY BUFFERPOOL (Db2) (Db2Commands)-ALTER BUFFERPOOL (Db2) (Db2 Commands)

DSNB402I BUFFER POOL SIZE = pool-sizeBUFFERS AUTOSIZE = autosizeVPSIZE MINIMUM = minimum sizeVPSIZE MAXIMUM = maximum-size ALLOCATED = allocated-buffers TO BE DELETED = delete-

buffers IN-USE/UPDATED =current-buffers

ExplanationThis message is a section of output from the DISPLAYBUFFERPOOL command, which is part of message“DSNB401I” on page 71.

DSNB404I THRESHOLDS — VP SEQUENTIAL =vpseq SP SEQUENTIAL = spseqDEFERRED WRITE = dwtVERTICAL DEFERRED WRT =dwv1,dwv2 PARALLELSEQUENTIAL = vppseqtASSISTING PARALLEL SEQT =vpxpseqt


DSNB406I PGFIX ATTRIBUTE - CURRENT =current-pgfix PENDING = pending-pgfix PAGE STEALING METHOD =current-pgsteal


DSNB408I NO DETAIL STATISTICSAVAILABLE FOR BUFFER POOL bp-name

ExplanationThis message is part of the output from the DISPLAYBUFFERPOOL command, which is part of message“DSNB401I” on page 71.

DSNB409I INCREMENTAL STATISTICS SINCEbase-time


DSNB410I CUMULATIVE STATISTICS SINCEbase-time


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_monitobufferpools.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_monitobufferpools.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_monitortunebufferpoolonlinecommands.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_monitortunebufferpoolonlinecommands.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displaybufferpool.html




DSNB411I RANDOM GETPAGE = rgp SYNCREAD I/O (R) = srr SYNC READ I/O(ZHL) = srrz SEQ. GETPAGE = sgpSYNC READ I/O (S) = srs DMTH HIT= dmt PAGE-INS REQ = pirSEQUENTIAL = seq VPSEQT HIT =vsh RECLASSIFY = rcy


DSNB412I SEQUENTIAL PREFETCH -REQUESTS = pft PREFETCH I/O =pio PAGES READ = pfp


DSNB413I LIST PREFETCH - REQUESTS = pftPREFETCH I/O = pio PAGES READ= pfp


DSNB414I DYNAMIC PREFETCH - REQUESTS= pft PREFETCH I/O = pio PAGESREAD = pfp


DSNB415I PREFETCH DISABLED - NOBUFFER = pfd NO READ ENGINE =ree


DSNB420I SYS PAGE UPDATES = pages-updated SYS PAGES WRITTEN =pages-written ASYNC WRITE I/O =async-writes SYNC WRITE I/O =sync-writes PAGE-INS REQUIRED= page-ins


DSNB421I DWT HIT= dwt VERTICAL DWTHIT=vdw


DSNB431I SIMULATED BUFFER POOL SIZE =pool-size BUFFERS ALLOCATED =allocated-buffers IN-USE = current-buffers HIGH IN-USE = high-in-useSEQ-IN-USE = current-sequential-buffers HIGH SEQ-IN-USE = high-sequential-buffers


DSNB432I - SIMULATED BUFFER POOLACTIVITY -


Related conceptsBuffer pool simulation results (Db2Performance)Related reference-DISPLAY BUFFERPOOL (Db2) (Db2Commands)

DSNB440I PARALLEL ACTIVITY — PARALLELREQUEST = tpa DEGRADEDPARALLEL = dpa


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_bpsimulationresults.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_bpsimulationresults.html




DSNB441I LPL ACTIVITY - PAGES ADDED =pages


DSNB453I VP CACHED PAGES - CURRENT =vcount MAX = mvcount CHANGED =ccount MAX = mccount


DSNB455I SYNCHRONOUS I/O DELAYS —AVERAGE DELAY = avd MAXIMUMDELAY = mxd TOTAL PAGES = tpgSYNCHRONOUS I/O DELAYS WITHZHYPERLINK — AVERAGE DELAY =avdz MAXIMUM DELAY = mxdzTOTAL PAGES = tpgz


DSNB456I ASYNCHRONOUS I/O DELAYS —AVERAGE DELAY = avd MAXIMUMDELAY = mxd TOTAL PAGES = tpgTOTAL I/O COUNT = tio


DSNB457I NUMBER OF PAGES IN THESIMULATED BUFFER POOLCURRENT = scount MAX = mscount


DSNB459I csect-name OPEN FAILURE HASOCCURRED FOR DATASET dsn

ExplanationThis message is output from the DISPLAYBUFFERPOOL command, which is part of message“DSNB401I” on page 71.

DSNB460I PAGE SET/PARTITION LISTINFORMATION


DSNB463I * * * NO OBJECTS MATCHED LIST/LSTATS SELECTION CRITERIA

ExplanationThis message is output from the DISPLAYBUFFERPOOL command, which is part of message“DSNB401I” on page 71.

DSNB464I PAGE SET/PARTITION LISTINFORMATION


DSNB466I ------------------PAGE SET/PARTITIONSTATISTICS-------------------


DSNB467I STATISTICS FOR object-typedatabase-name.space-nameINSTANCE instance-number DATASET #: set-number USE COUNT:application-count



DSNB468I keyword KEYWORD IS IGNOREDFOR NON-DATA SHARINGSYSTEMS

ExplanationThe identified keyword is valid only in a data-sharingenvironment. Keywords GBPDEP and CASTOWNR cancause this message to be displayed.

System actionThe command ignores the keyword and terminatesnormally.

User responseRe-enter the command without the keyword since theDb2 is a non-data-sharing Db2.

DSNB469I keyword1 KEYWORD IS IGNOREDWHEN keyword2 KEYWORD ISSPECIFIED

Explanationkeyword1 is incompatible with keyword2. For example,consider the following command:

DIS BPOOL(BP0) GBPDEP(Y) LSTATS(*)

The GBPDEP keyword requests a list of page sets orpartitions (as in the LIST keyword); however, GBPDEPis ignored because LIST and LSTATS are two differentreports.

System actionThe command ignores keyword1 and terminatesnormally.

User responseOmit keyword1 if keyword2 is used on the next entry ofthe command.

Related reference-DISPLAY BUFFERPOOL (Db2) (Db2Commands)

DSNB499I DISPLAY TERMINATED DUE TOINSUFFICIENT MESSAGE SPACE

ExplanationThis message is included in the following output:

• Output from the DISPLAY BUFFERPOOL command,which is part of message “DSNB401I” on page 71

• Output from the DISPLAY GROUPBUFFERPOOLcommand, which is part of message “DSNB750I” onpage 97

Related reference-DISPLAY BUFFERPOOL (Db2) (Db2Commands)-DISPLAY GROUPBUFFERPOOL (Db2) (Db2Commands)

DSNB501I bpname IS NOT A VALID BUFFERPOOL NAME

ExplanationAn invalid buffer pool name was specified on an ALTERBUFFERPOOL or DISPLAY BUFFERPOOL command.THE VALID NAMES ARE BP0, BP1,..., BP49, BP32K,BP32K1,...BP32K9.

System actionThe request is rejected.

System programmer responseReissue the ALTER BUFFERPOOL or DISPLAYBUFFERPOOL command, specifying a valid buffer poolname.

DSNB502I ENCOUNTERED AN ERROR WHILEVALIDATING INPUT vp-parm FORbp-name MUST BE BETWEENlower-limit AND upper-limit .SPECIFIED VALUE IS specified-value.

ExplanationAn ALTER BUFFERPOOL command was issued thatspecified incompatible values for one or more of thefollowing options: VPSIZE, VPSIZEMIN, orVPSIZEMAX.vp-parm

The option for which an incompatible value wasspecified. VPSIZE, VPSIZEMIN, VPSIZEMAX

bp-nameBuffer pool name.

lower-limitLower limit for the VPSIZE value for a buffer pool.The same limit applies to the VPSIZEMIN value fora buffer pool. For BP0, the lower limit is 2000. ForBP8K0, the lower limit is 1000. For BP16K0, thelower limit is 500. For all other buffer pools, thelower limit is 0.






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displaygroupbufferpool.html


upper-limitUpper limits for the VPSIZE of a buffer pool. Thesame limit applies to the VPSIZEMAX value for abuffer pool. The upper limit is based on the page-size of the buffer pool:

• 250000000 for 4KB page-size buffer pools• 125000000 for 8KB page-size buffer pools• 62500000 for 16KB page-size buffer pools• 31250000 for 32KB page-size buffer pools

specified-valueThe value that is specified for VPSIZE, VPSIZEMINor VPSIZEMAX in the ALTER BUFFERPOOLcommand.

System actionThe buffer pool is not modified.

System programmer responseReissue the ALTER BUFFERPOOL command, andspecify a valid value for compatible values for VPSIZE,VPSIZEMIN, and VPSIZEMAX.

Related reference-ALTER BUFFERPOOL (Db2) (Db2 Commands)

DSNB504I VPSEQT FOR bpname MUST BEBETWEEN 0 AND 100

ExplanationAn ALTER BUFFERPOOL command was issued to try toalter a buffer pool's VPSEQT attribute to an invalidvalue. VPSEQT is the buffer pool sequential stealthreshold. Valid values range 0 - 100.


System programmer responseReissue the ALTER BUFFERPOOL command, specifyinga legitimate VPSEQT value.

DSNB506I DWQT FOR bpname MUST BEBETWEEN 0 AND 90

ExplanationAn attempt was made to change a buffer pool's DWQTattribute value using the ALTER BUFFERPOOLcommand. DWQT is the free buffer deferred writethreshold. Valid values range 0 - 90.


System programmer responseReissue the ALTER BUFFERPOOL command, specifyinga legitimate DWQT value.

DSNB507I VDWQT FOR bpname MUST BEBETWEEN 0 AND 90

ExplanationAn attempt was made to change a buffer pool'sVDWQT attribute to an invalid value using the ALTERBUFFERPOOL command. VDWQT is the verticaldeferred write threshold. Valid values range 0 - 90.


System programmer responseReissue the ALTER BUFFERPOOL command, specifyinga legitimate VDWQT value.

DSNB508I csect-name THE TOTAL VPSIZEAND SPSIZE IS BEYOND THEMAXIMUM LIMIT

ExplanationAn ALTER BUFFERPOOL command specified a VPSIZEor SPSIZE value that would cause the sum of thessnmDBM1 address space storage requirements for allbuffer pools and simulated buffer pools to exceed 1TB.When calculating the storage requirements for thebuffer pools, Db2 uses the page size (4K, 8K, 16K, or32K) for each pool buffer.

System actionThe VPSIZE value or SPSIZE value for the buffer poolis not changed. Processing for other parametersproceeds normally.

System programmer responseRebalance VPSIZE or SPSIZE for all buffer pools.

DSNB510I NO ACTION REQUESTED

ExplanationAn ALTER BUFFERPOOL command was issued, but nobuffer pool attributes were specified.



System actionThe buffer pool's attributes are not changed.

System programmer responseReissue the ALTER BUFFERPOOL command specifyingone or more buffer pool attributes.

DSNB511I VDWQT CANNOT BE GREATERTHAN DWQT

ExplanationAn ALTER BUFFERPOOL command specified a DWQTand/or VDWQT value that would result in the bufferpool's VDWQT parameter being greater than its DWQTparameter.

System actionThe buffer pool's VDWQT or DWQT is not changed.Processing for other parameters, if requested,proceeds normally.

System programmer responseRebalance DWQT and VDWQT for the buffer pool.

DSNB512I integer IS THE CURRENT VPSIZEFOR BUFFER POOL bpname

ExplanationAn ALTER BUFFERPOOL command specified a VPSIZEequal to the buffer pool's current buffer pool size.

System actionThe buffer pool size is not changed. Processing forother parameters, if requested, proceeds normally.

DSNB514I integer IS THE CURRENT VPSEQTFOR BUFFER POOL bpname

ExplanationAn ALTER BUFFERPOOL command specified anVPSEQT equal to the current sequential stealthreshold of the buffer pool.

System actionThe buffer pool sequential threshold is not changed.Processing for other parameters, if requested,proceeds normally.

DSNB516I integer IS THE CURRENT DWQTFOR BUFFER POOL bpname

ExplanationAn ALTER BUFFERPOOL command specified a DWQTequal to the current deferred write threshold of thebuffer pool.

System actionThe deferred write threshold of the buffer pool is notchanged. Processing for other parameters, ifrequested, proceeds normally.

DSNB517I int1,int2 IS THE CURRENT VDWQTFOR BUFFER POOL bpname

ExplanationAn ALTER BUFFERPOOL command specified a VDWQTequal to the current vertical deferred write thresholdof the buffer pool.

System actionThe vertical deferred write threshold of the buffer poolis not changed. Processing for other parameters, ifrequested, proceeds normally.

DSNB519I csect-name PGSTEAL FORbufferpool-name HAS BEEN SET TOnew-pgsteal.

ExplanationThis message is issued in response to an ALTERBUFFERPOOL command to indicate that the requestedchange to the PGSTEAL parameter was accepted.


command-nameThe name of the z/OS MVS command that wasissued: START, STOP, or MODIFY. The MODIFYcommand refreshes the Db2 health monitor.

bufferpool-nameThe name of the buffer pool.

new-pgstealThe page stealing method (PGSTEAL) that will beused for the buffer pool.LRU

The buffer pool buffers are managed using theleast recently used (LRU) algorithm. This is thedefault option.

FIFOThe buffer pool buffers are managed using thefirst-in, first-out (FIFO) algorithm.


NONEThe buffer pool buffers are managed with theno-stealing algorithm. Objects that use thisbuffer pool are kept resident.



DSNB520I READY TO EXPLICITLY DELETEBUFFER POOL bpname

ExplanationThis message is issued before draining an active bufferpool in response to an ALTER BUFFERPOOL command,which specified VPSIZE=0 against an active bufferpool.

System actionAfter this message is issued, Db2 quiesces all currentactivities against this buffer pool. Db2 locks the tablespace exclusively and performs physical close for allopen table spaces or index spaces that reference thispool. Db2 also prevents subsequent database accessthat references this pool. SQL applications get anSQLCODE -904 (resource not available) with reasoncode 00C200E0 to indicate that the requested bufferpool size is not initialized. After the requested bufferpool is deleted, message DSNB521I is issued.

DSNB521I BUFFER POOL bpname HAS BEENEXPLICITLY DELETED

ExplanationThis message is issued after an active buffer pool isexplicitly deleted with an ALTER BUFFERPOOLcommand. This message is always preceded by acorresponding DSNB520I message.

System actionThe virtual storage that is associated with this bufferpool is released.

DSNB522I specified-option FOR bp-name HASBEEN SET

ExplanationThis message is issued in response to an ALTERBUFFERPOOL command to indicate that the requestedchange to the specified option was accepted. For anactive pool, the actual expansion, contraction, or

deletion does not take place until after this message isissued.specified-option

One of the following options that was specified inthe ALTER BUFFERPOOL command:

• VPSIZE• SSIZE• SPSEQT• VPMIN (for VPSIZEMIN)• VPMAX (for VPSIZEMAX)• FRAME (for FRAMESIZE)

bp-nameThe name of the buffer pool.


System programmer responseIssue the DISPLAY BUFFERPOOL command todetermine the actual virtual storage usage for thispool.

Related reference-ALTER BUFFERPOOL (Db2) (Db2 Commands)-DISPLAY BUFFERPOOL (Db2) (Db2Commands)

DSNB524I VPSEQT FOR bpname HAS BEENSET TO integer

ExplanationThis message is issued in response to an ALTERBUFFERPOOL command. It indicates the successfulmodification of the sequential steal threshold of thebuffer pool.

DSNB526I DWQT FOR bpname HAS BEEN SETTO integer

ExplanationThis message is issued in response to an ALTERBUFFERPOOL command. It indicates the successfulmodification of the deferred write threshold of thebuffer pool.

DSNB527I VDWQT FOR bpname HAS BEENSET TO int1,int2

ExplanationThis message is issued in response to an ALTERBUFFERPOOL command. It indicates the successful






modification of the vertical deferred write threshold ofthe buffer pool.

DSNB529I VPPSEQT FOR bpname HAS BEENSET TO integer

ExplanationThis message is issued in response to the ALTERBUFFERPOOL command. It indicates the successfulmodification of the parallel sequential steal thresholdof the buffer pool.

DSNB530I integer IS THE CURRENT VPPSEQTFOR BUFFER POOL bpname

ExplanationAn ALTER BUFFERPOOL command specified aVPPSEQT equal to the current parallel sequential stealthreshold of the buffer pool.

System actionThe parallel sequential steal threshold of the bufferpool is not changed. Processing for other parameters,if requested, proceeds normally.

DSNB531I VPPSEQT FOR bpname MUST BEBETWEEN 0 AND 100

ExplanationAn ALTER BUFFERPOOL command was issued to altera buffer pool's VPPSEQT attribute to an invalid value.VPPSEQT is the parallel sequential steal threshold ofthe buffer pool. Valid values range 0 - 100.

System actionThe VPPSEQT value is not changed.

System programmer responseChange the VPPSEQT attribute to a valid value andreenter the command.

DSNB532I VPXPSEQT FOR bpname HAS BEENSET TO integer

ExplanationThis message is issued from DSNB1ABP csect inresponse to the ALTER BUFFERPOOL command. Itindicates the successful modification of the assistingparallel sequential threshold of the buffer pool.

DSNB533I integer IS THE CURRENTVPXPSEQT FOR BUFFER POOLbpname

ExplanationAn ALTER BUFFERPOOL command specified aVPXPSEQT equal to the current assisting parallelsequential threshold of the buffer pool.

System actionThe assisting parallel sequential threshold of thebuffer pool is not changed. Processing for otherparameters, if requested, proceeds normally.

DSNB534I VPXPSEQT FOR bpname MUST BEBETWEEN 0 AND 100

ExplanationAn ALTER BUFFERPOOL command was issued tochange a buffer pool's VPXPSEQT attribute to aninvalid value. VPXPSEQT is the assisting parallelsequential threshold of the virtual buffer pool. Validvalues range 0 - 100. This message is issued fromDSNB1ABP csect.

System actionThe VPXPSEQT value is not changed.

System programmer responseChange the VPXPSEQT attribute to a valid value andreenter the command.

DSNB536I csect-name THE TOTAL VIRTUALBUFFER POOL STORAGE EXCEEDSTHE REAL STORAGE CAPACITY

ExplanationThis message is issued as a warning that the totalamount of allocated virtual buffer pool storage for thisDb2 subsystem has exceeded the real storage capacityof the z/OS image. The amount of real storage shouldbe at least as much as the total amount of virtualbuffer pool storage, and should also be enough toaccommodate the EDM pool and Db2 working storagein addition to the virtual buffer pool storage. Pagingactivity in the buffers is an indication of a performanceproblem.


System programmer responseAllocate more real storage to the z/OS image. If thereis not enough real storage to hold the buffers, then thenumber of buffers needs to be reduced. This might


mean fewer concurrent users. If the number of buffersis reduced, then Db2 will issue the DSNB538Imessage when the total amount of virtual buffer poolstorage no longer exceeds the real storage capacity.

DSNB538I csect-name THE TOTAL BUFFERPOOL STORAGE NO LONGEREXCEEDS THE REAL STORAGECAPACITY

ExplanationThis message is issued following a previous DSNB536Imessage to indicate that the total amount of allocatedbuffer pool storage for this Db2 subsystem no longerexceeds the real storage capacity of the z/OS image.


DSNB539I csect-name AUTOLPL FOR bpnameHAS BEEN SET TO value. IT WILLTAKE EFFECT ON THE NEXTALLOCATION

ExplanationDb2 issues this message in response to an ALTERBUFFERPOOL command to ind that the requestedchange to the AUTOLPL parameter was accepted. Thenew AUTOLPL value takes effect the next time thebuffer pool is allocated.

bpname is the name of the buffer pool.

value is one of the following:YES

Db2 automatically recovers pages that are in LPLstatus.

NODb2 does not automatically recover pages in LPLstatus. To recover the LPL page, perform one of thefollowing actions:

• Issue the START DATABASE command with theSPACENAM option

• Run the RECOVER or LOAD utility

System actionProcessing continues

DSNB540I csect-name INSUFFICIENT LOCALCACHE VECTOR STORAGE TOEXPAND BUFFER POOL bpname TOSPECIFIED SIZE size1. BUFFERPOOL SIZE IS NOW size2.

ExplanationThe specified buffer pool could not be expanded to therequested size (size1). The associated group bufferpool is connected, and the local cache vector could notbe expanded to cover the requested buffer pool size.

The local cache vector is a bit array which trackswhether the page in a given buffer was modified byanother system (cross-invalidated). There must be onebit in the vector for each buffer in the buffer pool. Formore information on the local cache vector, see z/OSMVS Programming: Sysplex Services Reference.

System actionDb2 downgrades the expansion request to the sizethat can be supported by the available local cachevector storage (size2).

System programmer responseFree local cache vector storage by contracting ordeleting other buffer pools that are connected to agroup buffer pool. Then reattempt the pool expansionby reissuing the ALTER BUFFERPOOL command.

DSNB541I csect-name THE TOTAL ACTIVEPGFIX YES BUFFER POOLSTORAGE EXCEEDS THE DB2ALLOWED REAL STORAGECAPACITY WHEN ALLOCATINGSTORAGE FOR BUFFER POOLbpname REAL STORAGE CAPACITY= rsc MB.

ExplanationWhen allocating storage for a PGFIX YES buffer pool,Db2 detects that the total storage allocated for thePGFIX YES buffer pools will exceed 80% of the realstorage capacity on this z/OS image. The buffer poolname identified on this message (bpname) will beallocated with the PGFIX NO attribute. The realstorage capacity of this z/OS image (rsc) is displayed inthis message in units of megabytes (1 MB = 2**20bytes).

System actionThe buffer pool is created using the PGFIX NOattribute.

System programmer responseEither allocate more real storage to this z/OS image,reduce the requested size of the buffer pool or use thePGFIX NO attribute.


Related tasksFixing a buffer pool in real storage (Db2Performance)Related reference-ALTER BUFFERPOOL (Db2) (Db2 Commands)

DSNB542I csect-name THE TOTAL ACTIVEPGFIX YES BUFFER POOLSTORAGE EXCEEDS THE DB2ALLOWED REAL STORAGECAPACITY WHEN EXPANDINGSTORAGE FOR BUFFER POOLbpname CURRENT VPSIZE =cbpsize NEW VPSIZE = nbpsizeREAL STORAGE CAPACITY = rscMB.

ExplanationWhen expanding the VPSIZE for an active PGFIX YESbuffer pool, Db2 detects that the total storageallocated for all active PGFIX YES buffer pools willexceed 80% of the real storage capacity on this z/OSimage. The ALTER BUFFERPOOL command fails andthe buffer pool will continue to be active with thecurrent VPSIZE value.

The buffer pool attributes and real storage capacityare:bpname

The buffer pool name.cbpsize

The current VPSIZE for the buffer pool.nbpsize

The new VPSIZE that was specified on the ALTERBUFFERPOOL command.

rscThe real storage capacity of this z/OS image inunits of megabytes (1 MB = 2**20 bytes).

System actionThe ALTER BUFFERPOOL command fails. The bufferpool continues to be active with the current VPSIZE.

System programmer responseEither allocate more real storage to this z/OS image,reduce the requested size of the buffer pool or use thePGFIX NO attribute.

DSNB543I THE PGFIX ATTRIBUTE ISALTERED FOR BUFFER POOL bp-name CURRENT ATTRIBUTE =current-pgfix NEW ATTRIBUTE =new-pgfix THE NEW ATTRIBUTE ISIN PENDING STATE.

ExplanationAn ALTER BUFFERPOOL command requested a changeto the PGFIX attribute and the change was accepted.The new value will take effect the next time the bufferpool is allocated.

bp-nameThe buffer pool name.

current-pgfixThe current PGFIX value for the buffer pool.

new-pgfixThe new PGFIX value that was specified on theALTER BUFFERPOOL command.


Related tasksFixing a buffer pool in real storage (Db2Performance)Choosing a page-stealing algorithm (Db2Performance)Related reference-ALTER BUFFERPOOL (Db2) (Db2 Commands)

DSNB544I AUTOSIZE FOR bpname HAS BEENSET TO nasize

ExplanationThis message is issued in response to an ALTERBUFFERPOOL command to indicate that the requestedchange to the AUTOSIZE attribute has been accepted.

bpnameThe buffer pool name.

nasizeThe new AUTOSIZE value specified in the ALTERBUFFERPOOL command, either YES or NO.


DSNB545I FOR bp-name, VPSIZE specified-value NOT VALID WITHVPSIZEMIN minimum-size ANDVPSIZEMAX maximum-size.VPSIZE MUST BE BETWEENVPSIZEMIN AND VPSIZEMAX

ExplanationAn ALTER BUFFERPOOL command was issued thatspecified incompatible values for one or more ofVPSIZE, VPSIZEMAX, or VPSIZEMIN. The value of










VPSIZE must be greater than or equal to the value ofVPSIZEMIN, and less than or equal to the value ofVPSIZEMAX.

bp-nameThe name of the buffer pool.

specified-valueThe value that is specified for VPSIZE in the ALTERBUFFER POOL command or if no value wasspecified, the current value.

minimum-sizeThe value that is specified for VPSIZEMIN in theALTER BUFFER POOL command or if no value wasspecified, the current value.

maximum-sizeThe value that is specified for VPSIZEMAX in theALTER BUFFER POOL command or if no value wasspecified, the current value.

System actionThe buffer pool is not modified.

User responseReissue the ALTER BUFFERPOOL command, andspecify compatible values for the VPSIZE, VPSIZEMINand VPSIZEMAX options.


DSNB546I PREFERRED FRAME SIZEpreferred-size buffer-countBUFFERS USING frame-sizeFRAME SIZE ALLOCATED


DSNB547I SPSEQT FOR bpname MUST BEBETWEEN 0 AND 100

ExplanationAn ALTER BUFFERPOOL command was issued to altera buffer pool's SPSEQT attribute to an invalid value.SPSEQT is the sequential steal threshold for thesimulated buffer pool. Valid values range from 0 to100.

The buffer pool attributes are:bpname

The buffer pool name.

System actionThe SPSEQT value is not changed.

System programmer responseChange the SPSEQT attribute to a valid value, andreenter the command.

DSNB551I BSDS READ ERROR, RC= integer,RSN=integer

ExplanationThis message is issued in response to a failure of aREAD function on the bootstrap data set (BSDS). Usersshould check any previous error messages issued byMVS and Db2 against the corresponding BSDS. RC andRSN indicate an error return code and reason codefrom the BSDS function.



System programmer responseAnalyze the return and reason codes to determinewhat type of error occurred. Refer to messageDSNJ107I for more information.

DSNB552I BSDS WRITE ERROR, RC= integer,RSN= integer

ExplanationThis message is issued in response to a failure of aWRITE function on the bootstrap data set (BSDS).Check any previous error messages issued by MVS andDb2 against the corresponding BSDS. RC and RSNindicate an error return code and reason code from theBSDS function.





System programmer responseAnalyze the return and reason codes to determinewhat type of error occurred. Refer to messageDSNJ108I for more information.

DSNB553I BSDS INSERT ERROR, RC= integer,RSN= integer

ExplanationThis message is issued in response to a failure of anINSERT function on the bootstrap data set (BSDS).Check any previous error messages issued by MVS andDb2 against the corresponding BSDS. RC and RSNindicate an error return code and reason code from theBSDS function.



System programmer responseAnalyze the return and reason codes to determinewhat type of error occurred. For more information,refer to message DSNJ109I or other DSNJ messagesrelated to BSDS.

DSNB555I WLM RECOMMENDATION TOADJUST SIZE FOR BUFFER POOLbpname HAS COMPLETED OLDSIZE = csize BUFFERS NEW SIZE =nsize BUFFERS

ExplanationThis message is issued when Workload Manager(WLM) notifies Db2 to adjust the size of a buffer pool.This recommendation is made based on WLM'sdynamic monitoring of the effects of buffer pool I/O onthe achievement of workload goals, and also on theamount of available storage on the system. Thismessage is issued after the adjustment hascompleted.

bpnameThe buffer pool name.

csizeThe old size of the buffer pool.

nsizeThe new size of the buffer pool.


DSNB601I BUFFER POOL bpname FULL

ExplanationA buffer is required to access a database page that isnot currently contained within the buffer pool. A buffercannot be assigned because all buffers in the bufferpool are in a nondisplaceable state. (Buffers are in anondisplaceable state when they contain activelyreferenced pages or updated pages for which writesare pending.)

This message can occur if there is an overload ofconcurrent activity for the buffer pool size. Thevariable bpname is the buffer pool external name.

System actionReason code 00C200E9 and the buffer pool externalname are recorded in the cursor table (CT), which isavailable in the SQL communication area (SQLCA) ormessages. An SQLCODE -904 (resource not available)is returned to the user.


System programmer responseDo one of the following:

• Reduce concurrent activity by reducing the numberof Db2 threads.

• Use the ALTER BUFFERPOOL command to increasethe size of the buffer pool.

DSNB602I UNABLE TO CREATE BUFFER POOLbpname. BUFFER POOL SIZE ISZERO

ExplanationAn attempt to create the buffer pool failed whileopening a Db2 table space or index that specified itsuse. The buffer pool size for bpname was zero. Thisindicates that the use of the pool is invalid.

System actionReason code 00C200E0 and the buffer pool externalname are recorded in the cursor table (CT), which isavailable in the SQL communication area (SQLCA) ormessages. An SQLCODE -904 (resource not available)is returned to the user.



System programmer responseUse the ALTER TABLESPACE or ALTER INDEXstatement to modify affected table spaces or indexesto indicate a usable buffer pool. Use the DISPLAYBUFFERPOOL command to determine a usable bufferpool. If necessary, use the ALTER BUFFERPOOLcommand to activate the failing buffer pool by settingits VPSIZE to a nonzero value.

DSNB603I INSUFFICIENT STORAGE TOCREATE/EXPAND BUFFER POOLbpname TO SPECIFIED SIZEinteger. BUFFER POOL SIZE ISNOW integer.

ExplanationA buffer pool could not be created or expanded to therequested size. Insufficient storage exists within thessnmDBM1 address space to build the buffer pool. Thebuffer pool size is set by the ALTER BUFFERPOOLcommand and can be queried by using the DISPLAYBUFFERPOOL command.

System actionThe buffer pool is created or expanded to the sizeallowed by the available storage. If the buffer poolcannot be created at all, and the creation request wastriggered by a page set open by an application, then anSQLCODE -904 (resource not available) is returned tothe user. Reason code 00C200E8 and the buffer poolexternal name are recorded in the cursor table (CT),which is available in the SQL communication area(SQLCA) or messages.


System programmer responseAnalyze the storage content of the ssnmDBM1 addressspace to determine further action. If appropriate, usethe ALTER TABLESPACE or ALTER INDEX statement touse a different buffer pool. Otherwise, use ALTERBUFFERPOOL commands to balance storage use for allbuffer pools.

DSNB605I UNABLE TO CREATE BUFFER POOLbpname TO SPECIFIED SIZEDURING STARTUP/RESTART.INSUFFICIENT VIRTUAL STORAGE

ExplanationAn attempt to create the buffer pool failed at the timethat Db2 was performing its startup or restartprocessing. Insufficient virtual storage exists withinthe ssnmDBM1 address space for building the bufferpool. The name of the buffer pool is bpname.

System actionThe buffer pool is not created. The table space orindex open request, which triggered the attempt tocreate the buffer pool, fails. An SQLCODE -904(resource not available) is returned to the user. Reasoncode 00C200E8 and the buffer pool external name arerecorded in the cursor table (CT), which is available inthe SQL communication area (SQLCA) or messages.


Operator responseNotify the system programmer. This message remainson the console until the operator deletes it.

System programmer responseAnalyze the virtual storage content of the DSNDBM1ssnmDBM1 address space to determine further action.If appropriate, use ALTER BUFFERPOOL commands tobalance virtual storage use for all buffer pools.

DSNB609I VIRTUAL BUFFER POOL bpnameCREATED USING DEFAULT SIZEDURING STARTUP/RESTART.VIRTUAL BUFFER POOL SIZE ISZERO

ExplanationWhile activating a buffer pool during Db2 startup orrestart processing, the buffer pool size was zero. Azero value might be caused by an unusable bootstrapdata set (BSDS) or by a Db2 abnormal terminationafter buffer pool size was altered to zero. The name ofthe buffer pool is bpname.

System actionDb2 creates the buffer pool using the startup restartdefault value.


Operator responseNotify the system programmer. This message remainson the console until deleted by the operator.


System programmer responseUse the ALTER TABLESPACE or ALTER INDEXstatement to modify the affected table spaces orindexes to indicate a usable buffer pool. To determinea usable buffer pool, use the DISPLAY BUFFERPOOLcommand. If necessary, use the ALTER BUFFERPOOLcommand to activate the failing buffer pool by settingthe VPSIZE to a nonzero value.

DSNB610I csect-name MAXIMUMALLOCATABLE BUFFER POOLSTORAGE OF int1MB HAS BEENREACHED. UNABLE TO CREATE/EXPAND BUFFER POOL bp-nameTO SPECIFIED SIZE int2. BUFFERPOOL IS NOW int3

ExplanationA buffer pool could not be created or expanded to therequested size. The maximum amount of allowablebuffer pool storage, indicated by int1, has beenreached. The maximum allowable buffer pool storageis calculated to be twice the amount of real storagethat is available on the z/OS image, or 1TB, whicheveris less.bpname

Indicates the name of the buffer pool that wasaffected.

int2Indicates the size of the buffer pool that wasrequested.

int3Indicates the actual size of the buffer pool thatwas created/expanded.

System actionThe buffer pool is created or expanded to the sizeallowed by the available storage within the maximum.If the maximum has already been reached, then thebuffer pool is allocated at a minimum size as follows:

• 2,000 pages for 4K page size• 1,000 pages for 8K page size• 500 pages for 16K page size• 250 pages for 32K page size

Once the maximum has been reached, buffer poolsizes are not allowed to be increased.

System programmer responseAnalyze the buffer pool sizes and determine if any canbe decreased, or consider adding more memory.

DSNB612I csect-name THE MAXIMUMAMOUNT OF BUFFER POOLSTORAGE HAS BEEN ALLOCATED.THE SIMULATED BUFFER POOLCANNOT BE CREATED OREXPANDED. BUFFER POOLbpname, MAXIMUM STORAGEmaximum-storage MB, STORAGENEEDED storage-needed MB.

ExplanationA simulated buffer pool could not be created orexpanded to the requested size. The maximumamount of virtual storage for buffer pools andsimulated buffer pools was reached. That value istwice the amount of real storage that is available onthe z/OS image, or 1TB, whichever is less.bpname

The name of the buffer pool that is to besimulated.

maximum-storageThe maximum amount of virtual storage for bufferpools and simulated buffer pools that is allowed.

storage-neededThe amount of virtual storage for buffer pools andsimulated buffer pools that is needed before thesimulated buffer pool can be created or expanded.

System actionThe simulated buffer pool is not created or expanded.

System programmer responseIssue DISPLAY BUFFERPOOL to obtain informationabout the buffer pool sizes. Analyze the existing bufferpool sizes, and the simulated buffer pool sizes that areneeded. Take one of the following actions:

• Determine if any other buffer pool sizes can bedecreased.

• Add more real memory, so that the virtual memorysize can be increased.

DSNB613I csect-name INSUFFICIENTVIRTUAL STORAGE TO CREATE OREXPAND THE SIMULATED BUFFERPOOL FOR bpname. REQUESTEDSIMULATED BUFFER POOL SIZEREQUIRES virtual-storage-size MB.

ExplanationA simulated buffer pool could not be created orexpanded to the requested size. Insufficient storage


exists in the ssnmDBM1 address space to build thesimulated buffer pool.bpname

The name of the buffer pool that is to besimulated.

virtual-storage-sizeThe amount of virtual storage, in MB, that isneeded to create or expand a simulated bufferpool of the requested size.

System actionThe simulated buffer pool is not created or expanded.

System programmer responseTake one of the following actions:

• Specify a smaller simulated buffer pool size toreduce the amount of storage that the simulatedbuffer pool uses.

• Increase the amount of virtual storage that thessnmDBM1 address space uses.

DSNB614I csect-name SPSIZE FOR bpnameHAS BEEN SET TO ZERO BECAUSEPGSTEAL pgsteal-value IS NOTCOMPATIBLE WITH A SIMULATEDBUFFER POOL.

ExplanationAn ALTER BUFFERPOOL command was issued for oneof the following reasons:

• To change the PGSTEAL value for the buffer pool• To change the SPSIZE value for the simulated buffer

pool

The PGSTEAL value is incompatible with the SPSIZEvalue. The PGSTEAL value must be LRU for a simulatedbuffer pool.

bpnameThe name of the buffer pool that is to besimulated.

pgsteal-valueThe invalid PGSTEAL value.

System actionSPSIZE is set to zero. If the simulated buffer pool waspreviously allocated, it is deleted.

System programmer responseTo create the simulated buffer pool, issue the ALTERBUFFERPOOL command with a non-zero SPSIZE value,and a PGSTEAL value of LRU.

DSNB740I csect-name ATTEMPTING TOESTABLISH DUPLEXING FORGROUP BUFFER POOL gbpnameREASON = reason

ExplanationDb2 has been requested to establish duplexing for thenamed group buffer pool. reason indicates the reasonwhy duplexing was initiated. reason can be one of thefollowing:OPERATOR

The operator initiated a SETXCF command toinitiate duplexing.

POLICYThe currently active CFRM policy indicated thatduplexing should be automatically established forthe group buffer pool.

This message is issued by each Db2 memberparticipating in establishing duplexing.

System actionThe Db2 members that are actively connected to thenamed group buffer pool participate in establishingduplexing for the group buffer pool. Access to thegroup buffer pool is quiesced while duplexing is beingestablished.

DSNB741I csect-name DUPLEXING COULDNOT BE ESTABLISHED FOR GROUPBUFFER POOL gbpname REASON =reason

ExplanationDb2 was unable to establish duplexing for the namedgroup buffer pool. reason indicates the Db2 reasoncode indicating why duplexing could not beestablished.

System actionThe group buffer pool goes back to simplex mode.

System programmer responseSee the explanation for the reason code given.

DSNB742I csect-name DUPLEXING HAS BEENSUCCESSFULLY ESTABLISHED


FOR GROUP BUFFER POOLgbpname

ExplanationThe process to establish duplexing for the namedgroup buffer pool has successfully completed.

This message is preceded by message DSNB740Iwhich indicates the reason why duplexing wasinitiated. This message is issued by each Db2 memberparticipating in establishing duplexing.

System actionProcessing of mainline requests is resumed for thegroup buffer pool. Writes of changed pages to thegroup buffer pool will be duplexed writes from thispoint forward.

DSNB743I csect-name DUPLEXING IS BEINGSTOPPED FOR GROUP BUFFERPOOL gbpname FALLING BACK TOPRIMARY REASON = reason1 DB2REASON CODE = reason2

ExplanationDuplexing is being stopped for the named group bufferpool. To stop the duplexing, the secondary groupbuffer pool will be deallocated, and Db2 will go back tosimplex mode on the primary group buffer pool.

reason1 indicates why duplexing was stopped:OPERATOR

The operator initiated an MVS command to stopduplexing.

POLICYA new CFRM policy has been activated whichspecifies DUPLEX(DISABLED) for the group bufferpool.

LOSSCONNSECOne or more of the Db2 members lost connectivityto the secondary group buffer pool structure.

STRFAILSECThe secondary group buffer pool structure failed.

DB2REASONDb2 decided to stop duplexing. The reason codegiven in reason2 indicates why Db2 stoppedduplexing.

DUPCONNCHGDuplexing rebuild stopped because of insufficientconnectivity due to a change in the set ofconnectors.

If reason1 indicates 'DB2REASON', then reason2specifies a Db2 reason code that indicates why Db2

stopped duplexing. If reason1 is not 'DB2REASON',then reason2 is zero.

This message is issued by each Db2 memberconnected to the duplexed group buffer pool.

System actionThe secondary group buffer pool structure isdiscarded, and Db2 enters back into simplex mode onthe primary group buffer pool structure. IfDUPLEX(AUTO) is specified in the active CFRM policyfor the group buffer pool, then duplexing will beautomatically reinitiated, if duplexing is still possible.

System programmer responseIf the rebuild stopped because of "DB2REASON", seethe explanation for the reason code given. If duplexingis not automatically reinitiated and duplexing isneeded for the group buffer pool, then use the MVSSETXCF command to reestablish duplexing.

DSNB744I csect-name DUPLEXING IS BEINGSTOPPED FOR GROUP BUFFERPOOL gbpname, SWITCHING TOSECONDARY REASON = reason1DB2 REASON CODE = reason2

ExplanationDuplexing is being stopped for the named group bufferpool. To stop the duplexing, the primary group bufferpool will be deallocated, and Db2 will switch to thesecondary group buffer pool to go back to simplexmode.

reason1 indicates why duplexing was stopped:OPERATOR

The operator initiated an MVS command to stopduplexing.

POLICYA new CFRM policy has been activated whichspecifies DUPLEX(DISABLED) for the group bufferpool.

LOSSCONNPRIOne or more of the Db2 members lost connectivityto the primary group buffer pool structure.

STRFAILPRIThe primary group buffer pool structure failed.

DB2REASONDb2 decided to stop duplexing. The reason codegiven in reason2 indicates why Db2 stoppedduplexing.

If reason1 indicates 'DB2REASON', then reason2specifies a Db2 reason code that indicates why Db2


stopped duplexing. If reason1 is not 'DB2REASON',then reason2 is zero.

This message is issued by each Db2 memberconnected to the duplexed group buffer pool.

System actionThe primary group buffer pool structure is discarded,and Db2 enters back into simplex mode on thesecondary group buffer pool structure. IfDUPLEX(ENABLED) is specified in the active CFRMpolicy for the group buffer pool, then duplexing will beautomatically reinitiated, if duplexing is still possible.

System programmer responseIf the rebuild stopped because of "DB2REASON", seethe explanation for the reason code given. If duplexingis not automatically reinitiated and duplexing isneeded for the group buffer pool, then use the MVSSETXCF command to reestablish duplexing.

DSNB745I csect-name THE TRANSITIONBACK TO SIMPLEX MODE HASCOMPLETED FOR GROUP BUFFERPOOL gbpname

ExplanationThe named group buffer pool has completed thetransition from duplex mode back to simplex mode.

This message is preceded either by messageDSNB743I or by message DSNB744I which indicatesthe reason why duplexing was stopped. This messageis issued by each Db2 member connected to the groupbuffer pool.

System actionThe group buffer pool is now back in simplex modewhich means that writes of changed pages to thegroup buffer pool are now simplexed. IfDUPLEX(ENABLED) is specified in the active CFRMpolicy for the group buffer pool, then duplexing will beautomatically reinitiated, if duplexing is still possible.This would mean that the group buffer pool is onlytemporarily back into simplex mode (it is soon to beentered back into duplex mode).

DSNB749I GBPCACHE NO IS NOT ALLOWEDFOR GROUP BUFFER POOLgbpname BECAUSE IT ISDUPLEXED

ExplanationThis message is issued in response to an ALTERGROUPBUFFERPOOL command that requests a

change of the GBPCACHE attribute from YES to NO,but because the group buffer pool is duplexed, thechange from YES to NO is not allowed.

System actionThe request to change from GBPCACHE(YES) toGBPCACHE(NO) is rejected.

System programmer responseGBPCACHE(NO) and duplexing are mutually exclusive.If you want GBPCACHE(NO), then you must put thegroup buffer in simplex mode before specifyingGBPCACHE(NO). To put a duplexed group buffer poolin simplex mode, do any of the following procedures:

• Activate a new CFRM policy that specifiesDUPLEX(DISABLED) for the group buffer pool. This isthe preferred method if you do not intend to duplexthe group buffer pool again for awhile.

• Ensure that DUPLEX(AUTO) is not specified in theactive CFRM policy for the group buffer pool, andthen issue the MVS command SETXCFSTOP,REBUILD,DUPLEX.

DSNB750I DISPLAY FOR GROUP BUFFERPOOL gbpname FOLLOWS

ExplanationThis message displays output from the DISPLAYGROUPBUFFERPOOL command.


-DISPLAY GROUPBUFFERPOOL (Db2) (Db2Commands)Group buffer pool monitoring with the DISPLAYGROUPBUFFERPOOL command (Db2 Data SharingPlanning and Administration)

For each qualifying group buffer pool, one of thefollowing two messages is displayed:

DSNB750IDSNB750I DISPLAY FOR GROUP BUFFER POOLgbpname FOLLOWS

Message DSNB750I is displayed if Db2 was able toaccess information for the group buffer pool in thez/OS coupling facility resource management(CFRM) administrative policy.

gbpnameThe name of the group buffer pool.

DSNB751IDSNB751I MVS CFRM POLICY INFORMATIONNOT AVAILABLE FOR GROUP BUFFER POOLgbpname MVS IXCQUERY RETURN CODE =




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_gbpmonitorzdisplaycmd.html



retcode MVS IXCQUERY REASON CODE =reason A PARTIAL DISPLAY FOLLOWS

Message DSNB751I is displayed if Db2 could notretrieve the z/OS CFRM administrative policyinformation for the group buffer pool. Either thez/OS query request (IXCQUERY) did notsuccessfully complete, or the backing structure forthe group buffer pool is not defined in the z/OSCFRM administrative policy. Therefore, theinformation that is displayed for the group bufferpool is incomplete. For example, if the IXCQUERYrequest did not complete successfully, aconnection list is not displayed, even if theCONNLIST option was specified on the DISPLAYGROUPBUFFERPOOL command.

gbpnameThe name of the group buffer pool.

retcodeThe return code from IXCQUERY.

reasonThe reason code from IXCQUERY.

To determine the reason, see IXCQUERY Returnand Reason Codes .

The remaining output for each group buffer poolconsists of one or more of the following sections:

• DSNB755I and DSNB756I: Group buffer pool status• DSNB757I: CFRM policy status• DSNB758I and DSNB759I: Allocation details for the

group buffer pool• DSNB798I: Last checkpoint• DSNB799I: Secondary group buffer pool attributes• DSNB766I, DSNB767I, and DSNB769I: Connection

list• DSNB771I: Incremental member detail statistics• DSNB772I: Cumulative member detail statistics• DSNB773I and DSNB774I: Synchronous read

statistics• DSNB775I and DSNB789I: Prefetch read statistics• DSNB776I: Synchronous write statistics• DSNB777I: Asynchronous write statistics• DSNB778I and DSNB796I: Castout statistics• DSNB797I: Other interactions• DSNB764I and DSNB793I: Secondary group buffer

pool statistics• DSNB782I: Incremental group statistics• DSNB783I: Cumulative group statistics• DSNB784I and DSNB785I: Group read statistics• DSNB786I: Group write statistics

• DSNB787I: Group reclaims and castouts• DSNB788I: Cross-invalidation statistics• DSNB762I: Secondary group buffer pool details• DSNB815I and DSNB816I: P-lock status•

If Db2 cannot display certain information, one or moreof the following messages are included in the output:

• DSNB752I: Group detail statistics are not availablebecause a rebuild is in progress

• DSNB763I: The group buffer pool is not defined withGBPCACHE(NO)

• DSNB765I: No connection list• DSNB768I: No group buffer pools are defined with

GBPCACHE(NO)• DSNB770I: Member detail statistics are not

available• DSNB780I: Group detail statistics are not available

because the member is not connected• DSNB781I: Group detail statistics are not available

because the MVS IXLCACHE request failed• DSNB791I: The member is not connected• DSNB792I: No members are connected• DSNB794I: The member is not connected to any

group buffer pool• DSNB795I: No members are connected to any group

buffer pool

The DISPLAY GROUPBUFFERPOOL output ends withone of the following messages:

• DSNB790I: End of output• DSNB499I: Display terminated because ofinsufficient space

DSNB755I and DSNB756I: Group bufferpool statusMessage DSNB750I or DSNB751I is followed by adescription of the status of the group buffer pool.

DSNB755I - DB2 GROUP BUFFER POOL STATUS CONNECTED = status1 CURRENT DIRECTORY TO DATA RATIO = ratio1 PENDING DIRECTORY TO DATA RATIO = ratio2 CURRENT GBPCACHE ATTRIBUTE = gcache1 PENDING GBPCACHE ATTRIBUTE = gcache2DSNB756I - CLASS CASTOUT THRESHOLD = class-threshold1,class-threshold2 GROUP BUFFER POOL CASTOUT THRESHOLD = gbp-threshold % GROUP BUFFER POOL CHECKPOINT INTERVAL = interval MINUTES


http://www-01.ibm.com/support/knowledgecenter/search/IXCQUERY%20return%20codes?scope=SSLTBW

http://www-01.ibm.com/support/knowledgecenter/search/IXCQUERY%20return%20codes?scope=SSLTBW

RECOVERY STATUS = status1 AUTOMATIC RECOVERY = auto-recovery

status1An indication of whether the Db2subsystem onwhich the DISPLAY GROUPBUFFERPOOLcommand was issued is connected to the groupbuffer pool.YES

The Db2 subsystem is actively connected tothe group buffer pool.

NOThe Db2 subsystem is not actively connectedto the group buffer pool.

ratio1The ratio of the number of directory entries to thenumber of data pages, as specified for the currentallocation of the group buffer pool.

ratio2The requested ratio of directory entries to datapages to take effect at the next reallocation of thegroup buffer pool.

gcache1The value of the GBPCACHE attribute for thecurrent allocation of the group buffer pool.

gcache2The value of the GBPCACHE attribute to take effectat the next reallocation of the group buffer pool.

class-threshold1The threshold at which class castouts are to beinitiated. This value is expressed as a percentageof the group buffer pool size.

class-threshold2The threshold at which class castouts are to beinitiated. This value is expressed as an absolutenumber of buffers. class-threshold2 is used todetermine the threshold only if class-threshold1 iszero and class-threshold2 is nonzero. Otherwise,class-threshold1 is used to determine thethreshold.

gbp-thresholdThe threshold at which castouts are to be initiatedat the group buffer pool level. This value isexpressed as a percentage of the group buffer poolsize.

intervalThe time, in minutes, between successive groupbuffer pool checkpoints.

status1The recovery status for the group buffer pool.Possible values are:DAP

Damage assessment is pending. Db2 isassessing damage to the group buffer pool in

response to a coupling facility structure failure.The group buffer pool is temporarily stoppedby Db2 and is unavailable for use until Db2completes the damage assessment.

NORMALNo pending recovery action exists for thisgroup buffer pool.

auto-recoveryThe value of the AUTOREC attribute for the groupbuffer pool. Possible values are:YES

If the group buffer pool fails, Db2 is toautomatically initiate recovery for the objectsthat use this group buffer pool. YES is thedefault.

NODb2 is not to initiate automatic group bufferpool recovery. If the group buffer pool fails,issue Db2 START DATABASE commands torecover the objects.


-ALTER GROUPBUFFERPOOL (Db2) (Db2Commands)-START DATABASE (Db2) (Db2 Commands)How Db2 writes from the group buffer pool to disk(Db2 Data Sharing Planning and Administration)Group buffer pool thresholds (Db2 Data SharingPlanning and Administration)

DSNB757I: CFRM policy statusIf Db2retrieved z/OS CFRM policy information for thegroup buffer pool, the DISPLAY GROUPBUFFERPOOLcommand output includes information about thestructure that is associated with the group buffer pool.

DSNB757I - MVS CFRM POLICY STATUS FOR structure-name = status2 MAX SIZE INDICATED IN POLICY = psize KB DUPLEX INDICATOR IN POLICY = dupstat CURRENT DUPLEXING MODE = dupmode ALLOCATED = status1

structure-nameThe coupling facility structure name for this groupbuffer pool, such as DSNCAT_GBP0.

status2The z/OS global status of the coupling facilitystructure. Possible values are:NORMAL

The structure is defined in the current CFRMpolicy and has no current z/OS restrictions.

CHNGPA change is pending in the structure policy.





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_howdb2writegbpdisk.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_groupbpthresholds.html


psizeThe size (in KBs) of the coupling facility structure,as indicated in the CFRM policy definition.

dupstatThe duplexing attribute for the coupling facilitystructure, as indicated by the DUPLEX parameter inthe CFRM policy definition. Possible values areDISABLED, ENABLED, or ALLOWED.

dupmodeThe current duplex mode of the group buffer pool.Possible values are:SIMPLEX

The group buffer pool is in simplex mode.DUPLEX

The group buffer pool is in duplex mode.INTRAN

The group buffer pool is in a transition state,either from simplex mode to duplex mode, orfrom duplex mode to simplex mode. Therebuild status indicator in message DSNB758Igives information about the transition state.

status1An indication of whether the backing couplingfacility structure is allocated:YES

The coupling facility structure is allocated in acoupling facility.

NOThe coupling facility structure is not allocatedin any coupling facility.


Coupling facility structures (Db2 Installation andMigration)Defining coupling facility structures (Db2Installation and Migration)CFRM parameters for administrative data utility(z/OS MVS Setting Up a Sysplex)

DSNB758I and DSNB759I: Allocationdetails for the group buffer poolIf Db2 successfully queries the MVS CFRM policy anddetermines that the group buffer pool is allocated, theDISPLAY GROUPBUFFERPOOL command outputincludes allocation details.

DSNB758I - ALLOCATED SIZE = asize KB VOLATILITY STATUS = volstat REBUILD STATUS = rbldstat CFNAME = cfname CFLEVEL - OPERATIONAL = cflevel1 CFLEVEL - ACTUAL = cflevel2DSNB759I - NUMBER OF DIRECTORY ENTRIES = dir# NUMBER OF DATA PAGES = data# NUMBER OF CONNECTIONS = conn#

asizeThe size (in KBs) of the allocated group buffer poolstructure.

volstatThe volatility status of the backing group bufferpool structure for this group buffer pool. Possiblevalues are:VOLATILE

The backing coupling facility structure isvolatile.

NON-VOLATILEThe backing coupling facility structure is non-volatile.

rbldstatAn indication of whether the group buffer poolstructure is being rebuilt, and, if so, which part ofthe rebuild process is in progress. Possible valuesare:NONE

The structure is not being rebuilt.QUIESCE

The structure is being rebuilt and is currently inthe rebuild quiesce phase.

CONNECTThe structure is being rebuilt and is currently inthe rebuild connect phase.

CLEANUPThe rebuild process is complete, and theconnected Db2 members are making finalpreparations to use the new group buffer poolstructure.

If rbldstat is CLEANUP and the duplexingstatus in message DSNB757I is INTRAN, thegroup buffer pool is in the final stages ofmaking the transition from duplex mode backto simplex mode. The Db2 group is switching tothe secondary group buffer pool.

STOPPINGThe rebuild process is stopped, and theconnected Db2 members are makingpreparations to fall back to the original groupbuffer pool structure. If rbldstat is STOPPINGand the duplexing status in messageDSNB757I is INTRAN, the group buffer pool ismaking the transition from duplex mode backto simplex mode and reverting to the primarygroup buffer pool.

DUPLEXEDThe group buffer pool is in steady-stateduplexing mode.

SWITCHINGThe group buffer pool is in the initial phase ofmaking the transition from duplex mode back


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_cfstructures.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_definingcfstructures.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_definingcfstructures.html

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaf100/subcfrm.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaf100/subcfrm.htm

to simplex mode and switching to thesecondary group buffer pool.

cfnameThe name of the coupling facility in which thegroup buffer pool is allocated. If the group bufferpool is duplexed, cfname is the name of thecoupling facility that is associated with the primarygroup buffer pool.

cflevel1The minimum architectural level that Db2requested for the coupling facility in which thegroup buffer pool is allocated. This value might beless than the actual coupling facility level,indicated by cflevel2. This happens if a highercoupling facility level than cflevel1 is needed toperform coupling facility structure operations. Ifthe group buffer pool is duplexed, cflevel1 is thecoupling facility level that is associated with theprimary group buffer pool.

cflevel2The coupling facility level for the coupling facility inwhich this group buffer pool is allocated. If thegroup buffer pool is duplexed, cflevel2 is thecoupling facility level that is associated with theprimary group buffer pool.

dir#The number of directory entries that are allocatedfor the coupling facility structure.

data#The number of data pages that are allocated forthe coupling facility structure.

conn#The number of Db2 subsystems that are connectedto the coupling facility structure. This numberincludes both active connections and failed-persistent connections. If the DISPLAYGROUPBUFFERPOOL command includes theCONNLIST option, the details of the connectionstatus are listed in message DSNB767I.


Coupling facility structures (Db2 Installation andMigration)Planning for coupling facility availability for datasharing (Db2 Installation and Migration)Rebuild events (Db2 Installation and Migration)How Db2 recovers from coupling facility failures(Db2 Data Sharing Planning and Administration)

DSNB798I: Last checkpointIf Db2 determines, by successfully querying the MVSCFRM policy, that the group buffer pool is allocated,the DISPLAY GROUPBUFFERPOOL command outputincludes checkpoint information

DSNB798I - LAST GROUP BUFFER POOL CHECKPOINT timestamp GBP CHECKPOINT RECOVERY LRSN = lrsn STRUCTURE OWNER = member-name

timestampThe date and time of the last group buffer poolcheckpoint.

lrsnThe log record sequence number (LRSN) that wasrecorded by the last group buffer pool checkpoint.

member-nameThe name of the member that is the structureowner for the group buffer pool.

A value of UNKNOWN means that Db2 is not ableto determine which member is the structure ownerfor the group buffer pool. This condition occursonly in error situations. See the message that isassociated with that error.

The structure owner has the followingresponsibilities:

• Issue group buffer pool checkpoints.• Detect the group buffer pool castout threshold

(the GBPOOLT value) and initiate castout if thisthreshold is reached. (The structure ownerinitiates castout by notifying the page set orpartition castout owners.)

• Coordinate the damage assessment process ifthe group buffer pool fails.

• Coordinate the rebuild process for the groupbuffer pool.

DSNB799I: Secondary group buffer poolattributesIf the group buffer pool is duplexed and Db2successfully queried the MVS CFRM administrativepolicy, the DISPLAY GROUPBUFFERPOOL commandoutput includes the attributes of the secondary groupbuffer pool. This message is not displayed if the groupbuffer pool is in a transition state between simplexingand duplexing.

DSNB799I - SECONDARY GBP ATTRIBUTES ALLOCATED SIZE = ssize KB VOLATILITY STATUS = svolstat CFNAME = cfname CFLEVEL - OPERATIONAL = cflevel1 CFLEVEL - ACTUAL = cflevel2 NUMBER OF DIRECTORY ENTRIES = sdir#




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_plancfavailability.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_plancfavailability.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_monitorrebuildevent.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_recovercffailures.html


NUMBER OF DATA PAGES = sdata#

ssizeThe allocated size (in KBs) of the coupling facilitystructure for the secondary group buffer pool.

svolstatThe volatility status of the secondary group bufferpool. Possible values are:VOLATILE

The structure is volatile.NON-VOLATILE

The structure is non-volatile.cfname

The name of the coupling facility in which thegroup buffer pool is allocated. If the group bufferpool is duplexed, this value is the coupling facilityname that is associated with the primary groupbuffer pool.

cflevel1The coupling facility level from a Db2 functionalityperspective for the coupling facility in which thesecondary group buffer pool is allocated.

cflevel2The coupling facility level for the coupling facility inwhich the secondary group buffer pool is allocated.

sdir#The number of directory entries that are allocatedfor the secondary group buffer pool.

sdata#The number of data pages that are allocated forthe secondary group buffer pool.

DSNB766I, DSNB767I, and DSNB769I:Connection listIf the DISPLAY GROUPBUFFERPOOL commandincluded the CONNLIST option, the output includes alist of connections for the group buffer pool. OneDSNB767I message is issued for each definedconnection to the group buffer pool.

DSNB766I - THE CONNLIST REPORT FOLLOWSDSNB767I - CONNECTION NAME = conname , CONNECTION STATUS = status CONNECTOR'S RELEASE = connector-releaseDSNB769I - THE CONNLIST REPORT IS COMPLETE

connameThe name of the connection. Db2 subsystems usethe Db2 member name as the connection name.

statusThe status of the connection. Possible values are:A

Active.

FFailed-persistent.

DDually connected to both the original structureand the new structure while the group bufferpool structure is being rebuilt.

connector-releaseThis value is always 10100.


Protection of retained locks: failed-persistentconnections (Db2 Data Sharing Planning andAdministration)

DSNB771I: Incremental member detailstatisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL(INTERVAL) option, the outputincludes incremental statistics for the member.

DSNB771I - INCREMENTAL MEMBER DETAIL STATISTICS SINCE basetime

basetimeThe start time of the interval for which thestatistics were accumulated. This value is the timeof the previous DISPLAY GROUPBUFFERPOOLMDETAIL(INTERVAL) report for this Db2 member.If such a report does not exist, this value is thetime that the member first connected to the groupbuffer pool.

DSNB772I: Cumulative member detailstatisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL(*) option, the output includescumulative statistics for the member.

DSNB772I - CUMULATIVE MEMBER DETAIL STATISTICS SINCE basetime

basetimeThe start time of the interval for which thestatistics were accumulated. This value is the timethat this Db2 member first connected to the groupbuffer pool.

DSNB773I and DSNB774I: Synchronousread statisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL option, the output includessynchronous read statistics for the group buffer pool.The term synchronous means that the coupling facility


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_protectretainedlocks.html



interaction is done under the execution unit of the Db2user.

DSNB773I - MEMBER DETAIL STATISTICS SYNCHRONOUS READS DUE TO BUFFER INVALIDATION DATA RETURNED = r1 DATA NOT RETURNED = r2DSNB774I - DUE TO DATA PAGE NOT IN BUFFER POOL DATA RETURNED = r3 DATA NOT RETURNED = r4

The following values in message DSNB773I refer tosynchronous coupling facility read requests that areissued because the virtual buffer was marked invalid.

r1The number of times that data is successfullyreturned from the group buffer pool in response tothe request.

r2The number of times that data is not returned fromthe group buffer pool in response to the request.

The values in message DSNB774I refer tosynchronous coupling facility read requests that areissued because the required data was not in the bufferpool buffer.

r3The number of times that data is successfullyreturned from the group buffer pool in response tothe request.

r4The number of times that data is not returned fromthe group buffer pool in response to the request.

DSNB775I and DSNB789I: Prefetch readstatisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL option, the output includesprefetch read statistics.

DSNB775I - PREFETCH READS DATA NOT RETURNED = r5 DSNB789I - REGISTER PAGE LIST = r7 PAGES RETRIEVED = r8

r5The number of pages that were retrieved fromDASD, instead of the group buffer pool, in responseto the register page list (RPL) request.

The RPL feedback indicated that the page was notcached in the group buffer pool. Therefore, toavoid a coupling facility read request for the page,

Db2 retrieved the page directly from DASD. Nocoupling facility interactions are associated withthis r5 value.

r7The number of coupling facility requests to registerinterest in a list of pages. Db2 makes this requestwhen sequential or list prefetch is used and thefollowing conditions are met:

• The Db2 member is running on a particularservice level of MVS 5.2 or later.

• The group buffer pool is allocated in a couplingfacility with CFLEVEL=2 or higher.

r8The number of coupling facility requests toprefetch a page in the group buffer pool as a resultof feedback from the request to register a list ofpages.

DSNB776I: Synchronous write statisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL option, the output includessynchronous write statistics for the group buffer pool.The term synchronous means that the coupling facilityinteraction is done under the execution unit of the Db2user.

DSNB776I - SYNCHRONOUS WRITES CHANGED PAGES = w1 CLEAN PAGES = w2

w1The number of changed pages that were writtensynchronously to the coupling facility.

w2The number of clean pages that were writtensynchronously to the coupling facility.

DSNB777I: Asynchronous write statisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL option, the output includesasynchronous write and cross-invalidation statisticsfor the group buffer pool. The term asynchronousmeans that the coupling facility interaction is doneunder the execution unit of a Db2 system, such as witha prefetch operation.

DSNB777I - ASYNCHRONOUS WRITES CHANGED PAGES = changed-pages-count CLEAN PAGES = clean-pages-count FAILED WRITES DUE TO LACK OF STORAGE = failed-writes-count WRITE-AROUND


PAGES = write-around-count

changed-pages-countThe number of changed pages that were writtenasynchronously to the coupling facility.

clean-pages-countThe number of clean pages that were writtenasynchronously to the coupling facility.

failed-writes-countThe number of coupling facility write requests thatwere not completed because the group buffer pooldid not have enough storage.

write-around-countThe number of changed pages that are written todisk through group-buffer-pool write-aroundprotocol.


Relief from storage shortages in group buffer pools(Db2 for z/OS What's New?)

DSNB778I and DSNB796I: CastoutstatisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL option, the output includesgroup buffer pool statistics for castouts, checkpoints,and rebuild operations.

DSNB778I - CASTOUT THRESHOLDS DETECTED FOR CLASSES = t1 FOR GROUP BUFFER POOL = t2 GBP CHECKPOINTS TRIGGERED = k1 PARTICIPATION IN REBUILD = k2DSNB796I - CASTOUTS PAGES CASTOUT = c1 UNLOCK CASTOUT = c2 READ CASTOUT CLASS = c3 READ CASTOUT STATISTICS = c4 READ DIRECTORY INFO = c5

t1The number of times that the class castoutthreshold was detected.

t2The number of times that the group buffer poolcastout threshold was detected.

k1The number of group buffer pool checkpoints thatwere triggered.

k2The number of times that this memberparticipated in a rebuild of the group buffer poolstructure.

c1That number of pages that were cast out.

c2The number of requests to unlock a page forcastout.

c3The number of requests to determine which pages,from a particular page set or partition, must becast out because they are cached as changedpages. This request is issued either by the page setor partition castout owner, or, when the groupbuffer pool castout threshold is reached by thegroup buffer pool structure owner.

c4The number of coupling facility requests to castout statistics.

c5The number of requests to read directoryinformation. These requests are made duringgroup buffer pool checkpoints.


Group buffer pool thresholds (Db2 Data SharingPlanning and Administration)Group buffer pool checkpoint (Db2 Data SharingPlanning and Administration)How Db2 recovers from coupling facility failures(Db2 Data Sharing Planning and Administration)How Db2 writes from the group buffer pool to disk(Db2 Data Sharing Planning and Administration)How Db2 gathers checkpoint information (Db2 DataSharing Planning and Administration)

DSNB797I: Other interactionsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL option, the output includeslocal statistics on various operations.

DSNB797I - OTHER INTERACTIONS REGISTER PAGE = o1 UNREGISTER PAGE = o2 DELETE NAME = o3 READ STORAGE STATISTICS = o4 EXPLICIT CROSS INVALIDATIONS = o5 ASYNCHRONOUS GBP REQUESTS = o6


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/wnew/src/tpc/db2z_10_reliefgbpshortage.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/wnew/src/tpc/db2z_10_reliefgbpshortage.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_groupbpcheckpoint.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_groupbpcheckpoint.html





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_howgathercheckptinfo.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_howgathercheckptinfo.html

o1The number of requests to the coupling facility toregister interest in a single page.

o2The number of requests to the coupling facility toremove the registered interest in a single page.

o3The number of requests to the coupling facility todelete the directory entries that are associatedwith a set of pages.

o4The number of requests to the coupling facility toread the statistics counters that are associatedwith the structure. Db2 generally issues thisrequest once per group buffer pool checkpoint andonce per DISPLAY GROUPBUFFERPOOL commandwith the GDETAIL option.

o5The number of explicit cross-invalidations forpages in the group buffer pool.

o6The number of coupling facility requests to theprimary group buffer pool that were convertedfrom synchronous to asynchronous.

DSNB764I and DSNB793I: Secondarygroup buffer pool statisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the MDETAIL option and the group bufferpool is duplexed, the output includes statistics onrequests and writes to the secondary group bufferpool.

DSNB764I - DUPLEXING STATISTICS FOR secondary-gbpname WRITES FAILED DUE TO LACK OF STORAGE = s2 ASYNC COMPLETION CHECKS = s3DSNB793I - DELETE NAME LIST = s5 READ CASTOUT STATISTICS = s6 DELETE NAME = s7 OTHER ASYNCHRONOUS GBP REQUESTS = s8

secondary-gbpnameThe secondary group buffer pool name. This nameis the primary group buffer pool name (such asGBP0) suffixed with -SEC.

s2The number of times that a write request from thecoupling facility did not complete because thesecondary group buffer pool did not have enoughstorage.

s3The number of times that Db2 checked whether achanged page was written to the secondary groupbuffer pool, but the write operation was not yetcomplete. Thus, the transaction had to wait untilthe write to the secondary group buffer poolcompleted.

s5The number of requests to delete from thesecondary group buffer pool a set of pages thatwere recently cast out from the primary groupbuffer pool. If the group buffer pool was duplexedfor the entire reporting interval, this numbershould be roughly equal to the number of UNLOCKCASTOUT requests, as reported in messageDSNB796I.

s6The number of requests to check for orphaneddata entries in the secondary group buffer pool.Orphaned data entries are changed data entries inthe secondary group buffer pool without acorresponding changed data entry in the primarygroup buffer pool.

The group buffer pool structure owner periodicallyissues these requests to determine whetherorphaned data entries in the secondary groupbuffer pool need to be cleaned up. Orphaned dataentries are expected periodically and do notindicate a data inconsistency problem. Orphaneddata entries can be introduced by certaintransaction or system failures or by the unlikelycircumstance that new group buffer pool writeactivity occurred concurrently with castoutprocessing.

s7The number of requests to delete orphaned dataentries from the secondary group buffer pool. Thegroup buffer pool structure owner issues theserequests if it determines that orphaned dataentries need to be cleaned up.

s8The number of asynchronous coupling facilityrequests that were sent to the secondary groupbuffer pool. This number excludes the s3 value.


Characteristics of primary and secondary structures(Db2 Installation and Migration)How Db2 writes from the group buffer pool to disk(Db2 Data Sharing Planning and Administration)

DSNB782I: Incremental group statisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the GDETAIL(INTERVAL) option, the output


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_structurecharacteristics.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_structurecharacteristics.html



includes incremental statistics for the group bufferpool.

DSNB782I - INCREMENTAL GROUP DETAIL STATISTICS SINCE basetime

basetimeThe start time of the interval for which thestatistics were accumulated. This value is the timeof the previous DISPLAY GROUPBUFFERPOOLGDETAIL(INTERVAL) report from this Db2 member.If such a report does not exist, this value is thetime that the group buffer pool was allocated orreallocated.

DSNB783I: Cumulative group statisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the GDETAIL(*) option, the output includescumulative statistics for the group buffer pool.

DSNB783I - CUMULATIVE GROUP DETAIL STATISTICS SINCE basetime

basetimeThe start time of the interval for which thestatistics were accumulated. This value is the timethat the group buffer pool was first allocated orreallocated.

DSNB784I and DSNB785I: Group readstatisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the GDETAIL option, the output includes readstatistics for the group buffer pool.

DSNB784I - GROUP DETAIL STATISTICS READS DATA RETURNED = r1DSNB785I - DATA NOT RETURNED DIRECTORY ENTRY EXISTED = r2 DIRECTORY ENTRY CREATED = r3 DIRECTORY ENTRY NOT CREATED = r4, r5

r1The "read hit" counter. The number of times that apage was returned for a coupling facility readrequest.

r2The "read miss directory hit" counter. The numberof times that a coupling facility read requestspecified a page for which a directory entry exists,but no data was cached for that page. Data was notreturned for the coupling facility read request.

r3The "read miss name assigned" counter. Thenumber of times that a coupling facility readrequest specified a page for which a directoryentry was created. Data was not returned for thecoupling facility read request.

r4The "read miss assignment suppressed" counter.The number of times that a coupling facility readrequest specified a page for which no directoryentry exists and no directory entry was created.Data was not returned for the coupling facility readrequest.

r5The "read miss cache full" counter. The number oftimes that both of the following events occurred:

• A coupling facility read request specified a pagefor which no directory entry exists.

• A directory entry was not created because thegroup buffer pool did not have enough storage.

Data was not returned for the coupling facility readrequest.

DSNB786I: Group write statisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the GDETAIL option, the output includeswrite statistics for the group buffer pool.

DSNB786I - WRITES CHANGED PAGES = w1 CLEAN PAGES = w2 FAILED DUE TO LACK OF STORAGE = w3 CHANGED PAGES SNAPSHOT VALUE = p1

w1The "changed page write hit" counter. The numberof changed pages that were successfully written.

w2The "clean page write hit" counter. The number ofclean pages that were successfully written.

w3The "write miss cache full" counter. The number oftimes that a coupling facility write request was notcompleted because the group buffer pool did nothave enough storage.

p1The "total changed" counter. The current numberof changed pages. The number is captured at asingle point in time. This value is not affected bywhether the DISPLAY GROUPBUFFERPOOL outputis incremental or cumulative.


DSNB787I: Group reclaims and castoutsIf the DISPLAY GROUPBUFFERPOOL commandincluded the GDETAIL option, the output includesstatistics on reclaims and castouts for the group bufferpool.

DSNB787I - RECLAIMS FOR DIRECTORY ENTRIES = d1 FOR DATA ENTRIES = d2 CASTOUTS = c1

d1The "directory entry reclaim" counter. The numberof times that a name assignment required that adirectory entry be reclaimed by the couplingfacility.

d2The "data entry reclaim" counter. The number oftimes that a name assignment required that a datapage be reclaimed by the coupling facility.

c1The "castout" counter. The number of pages thatwere cast out of the group buffer pool.

DSNB788I: Cross-invalidation statisticsIf the DISPLAY GROUPBUFFERPOOL commandincluded the GDETAIL option, the output includescross-invalidation (XI) statistics for the group bufferpool.

DSNB788I - CROSS INVALIDATIONS DUE TO DIRECTORY RECLAIMS = x1 DUE TO WRITES = x2 EXPLICIT = x3

x1The "XI for directory reclaim" counter. The numberof times that a directory entry with registered Db2interest was reclaimed. Therefore, cross-invalidation occurred.

x2The "XI for write" counter. The number of timesthat a coupling facility write request caused cross-invalidation to occur for one or more registeredDb2 members.

x3The "XI for explicit invalidation" counter. Thenumber of times that cross-invalidation occurredfor one or more registered Db2 members, becauseit was explicitly requested by the coupling facility.


Group buffer pool size is too small (Db2 DataSharing Planning and Administration)How Db2 writes to the group buffer pool (Db2 DataSharing Planning and Administration)Too few directory entries (Db2 Data SharingPlanning and Administration)

DSNB762I: Secondary group buffer pooldetailsIf the DISPLAY GROUPBUFFERPOOL commandincluded the GDETAIL option, and the group bufferpool is duplexed, the output includes the followinginformation about the secondary group buffer pool:

• Statistics on writes to the secondary group bufferpool

• The total number of changed pages for thesecondary group buffer pool.

DSNB762I - DUPLEXING STATISTICS FOR secondary-gbpname WRITES CHANGED PAGES = changed-pages FAILED DUE TO LACK OF STORAGE = writes-full CHANGED PAGES SNAPSHOT VALUE = changed-pages-snapshot

secondary-gbpnameThe secondary group buffer pool name. This nameis the primary group buffer pool name (such asGBP0) suffixed with -SEC.

changed-pagesThe number of times that a coupling facility writerequest for a changed page completedsuccessfully.

If the group buffer pool was duplexed for the entirereporting interval, this number should be roughlyequal to the "changed page write hit" counter inmessage DSNB786I. However, these counts mightnot be the same because of timing windows ingathering these values or if previous transactionfailures occurred.

writes-fullThe number of times that a write request from thecoupling facility was not completed because of alack of storage in the secondary group buffer pool.

changed-pages-snapshotThe total changed counter and snapshot value ofthe current number of changed pages in thesecondary group buffer pool. This value is notaffected by whether the DISPLAYGROUPBUFFERPOOL output is incremental orcumulative.

If the group buffer pool is duplexed, this numbershould be roughly equal to the "totalchanged"counter in message DSNB786I. However,


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_groupbpistoosmall.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_groupbpistoosmall.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_howdb2writestogbp.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_howdb2writestogbp.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_toofewdirentries.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_toofewdirentries.html

these counts might not be the same because oftiming windows in gathering these values or ifprevious transaction failures occurred.


Duplexed structures (Db2 Installation andMigration)How updates are made in a data sharingenvironment (Introduction to Db2 for z/OS)

DSNB815I and DSNB816I: P-lock statusThe DISPLAY GROUPBUFFERPOOL command outputincludes the physical lock (P-lock) status for the groupbuffer pool. This P-lock information can be usefulwhen you are monitoring and tuning databaseperformance, especially in a data sharing environment.

DSNB815I - PAGE P-LOCK LOCK/UNLOCK, REQUESTS FOR SPACE MAP = nn REQUESTS FOR DATA PAGES = nn REQUESTS FOR INDEX LEAF = nn UNLOCK REQUESTS = nnDSNB816I - PAGE P-LOCK SUSPENSIONS/NEGOTIATIONS, SUSPENSIONS FOR SPACE MAP = nn P-LOCK SUSPENSIONS FOR DATA = nn P-LOCK SUSPENSIONS FOR INDEX LEAF = nn NEGOTIATIONS FOR SPACE MAP = nn P-LOCK NEGOTIATIONS FOR DATA PAGES = nn NEGITIATIONS FOR INDEX LEAF PAGES = nn

DSNB752I: Group detail statistics are notavailable because a rebuild is in progressDSNB752I - GROUP DETAIL STATISTICS ARE NOT AVAILABLE FOR THE GROUP BUFFER POOL BECAUSE A REBUILD IS IN PROGRESS

The DISPLAY GROUPBUFFERPOOL command includedthe GDETAIL option. However, Db2cannot retrievegroup statistics because the group buffer pool is beingrebuilt.

DSNB763I: The group buffer pool is notdefined with GBPCACHE(NO)DSNB763I - gbpname IS NOT DEFINED WITH GBPCACHE NO

The DISPLAY GROUPBUFFERPOOL command includedthe TYPE(NOCACHE) option and either one name or alist of names in the selection list. However, theindicated group buffer pool is not defined with the

GBPCACHE(NO) attribute, and therefore does not meetthe qualification to be included in the output.

gbpnameThe group buffer pool name.

The display is terminated for this group buffer pool. Ifthe command has other group buffer pool names toprocess, command processing continues.

This message is issued once for each group buffer poolthat does not match the criterion to be defined withGBPCACHE(NO).

DSNB765I: No connection listDSNB765I - NO CONNLIST REPORT IS GENERATED. THERE ARE NO CONNECTIONS TO THIS GROUP BUFFER POOL.

The DISPLAY GROUPBUFFERPOOL command includedthe CONNLIST option. However, no connectionscurrently exist to report for the group buffer pool.

DSNB768I: No group buffer pools aredefined with GBPCACHE(NO)DSNB768I - THERE ARE NO GROUP BUFFER POOLS DEFINED WITH GBPCACHE NO

The DISPLAY GROUPBUFFERPOOL command includedthe TYPE(NOCACHE) option and an asterisk (*) as theselection list. However, no group buffer pools aredefined with the GBPCACHE(NO) attribute.

Command processing is terminated.

DSNB770I: Member detail statistics are notavailableDSNB770I - MEMBER DETAIL STATISTICS ARE NOT AVAILABLE FOR THE GROUP BUFFER POOL. THIS DB2 HAS NEVER BEEN CONNECTED TO THE GROUP BUFFER POOL.

The DISPLAY GROUPBUFFERPOOL command includedthe MDETAIL option. However, member statistics arenot available for the requested group buffer poolbecause this member has not connected to the groupbuffer pool since it was started.

DSNB780I: Group detail statistics are notavailable because the member is notconnectedDSNB780I - GROUP DETAIL STATISTICS ARE NOT AVAILABLE FOR THE GROUP BUFFER POOL. THIS DB2 IS NOT CURRENTLY CONNECTED TO THE GROUP BUFFER POOL.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsduplexingstructure.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsduplexingstructure.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_updatesindatasharingenvironment.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_updatesindatasharingenvironment.html

The DISPLAY GROUPBUFFERPOOL command includedthe GDETAIL option. However, Db2 could not retrievegroup statistics because this Db2 member is notcurrently connected to the group buffer pool.

DSNB781I: Group detail statistics are notavailable because the MVS IXLCACHErequest failedDSNB781I - GROUP DETAIL STATISTICS ARE NOT AVAILABLE FOR THE GROUP BUFFER POOL. MVS IXLCACHE RETURN CODE = retcode MVS IXLCACHE REASON CODE = reason

The DISPLAY GROUPBUFFERPOOL command includedthe GDETAIL option. However, Db2 could not retrievegroup statistics because the statistics request(through the z/OS MVS IXLCACHE macro) did notsuccessfully complete.

retcodeThe return code from MVS for the statisticsrequest.

reasonThe reason code from MVS for the statisticsrequest.


IXLCACHE — Cache ServicesReturn and Reason Codes for IXLCACHEREQUEST=READ_STGSTATS

DSNB791I: The member is not connectedDSNB791I - THIS DB2 IS NOT CONNECTED TO gbpname

The DISPLAY GROUPBUFFERPOOL command includedthe TYPE(MCONN) option and either one name or a listof names in the selection list. However, the Db2member on which the DISPLAY GROUPBUFFERPOOLcommand was issued is not currently connected to thespecified group buffer pool.


The display is terminated for this group buffer pool. Ifthe command includes other group buffer pool namesto process, command processing continues.

DSNB792I: No members are connectedDSNB792I - NO DB2 IN THE GROUP IS CONNECTED TO gbpname

The DISPLAY GROUPBUFFERPOOL command includedthe TYPE(GCONN) option and either one name or a listof names in the selection list. However, no Db2

member in the group is connected to the specifiedgroup buffer pool.


The display is terminated for this group buffer pool. Ifthe command includes other group buffer pool namesto process, command processing continues.

DSNB794I: The member is not connectedto any group buffer poolDSNB794I - THIS DB2 IS NOT CONNECTED TO ANY GROUP BUFFER POOL

The DISPLAY GROUPBUFFERPOOL command includedthe TYPE(MCONN) option and an asterisk (*) as theselection list. However, the Db2 member on which theDISPLAY GROUPBUFFERPOOL command was issued isnot connected to any group buffer pools.


DSNB795I: No members are connected toany group buffer poolDSNB795I - NO DB2 IN THE GROUP IS CONNECTED TO ANY GROUP BUFFER POOL

The DISPLAY GROUPBUFFERPOOL command includedthe TYPE(GCONN) option and an asterisk (*) as theselection list. However, no group buffer pools areconnected to any Db2 members in the data sharinggroup.


DSNB790I: End of outputThe following message indicates the end of the outputfrom the DISPLAY GROUPBUFFERPOOL command.

DSNB790I - DISPLAY FOR GROUP BUFFER POOL gbpname IS COMPLETE


DSNB499I: Display terminated because ofinsufficient spaceIf the DISPLAY GROUPBUFFERPOOL output is toolong, the output ends with message DSNB499I. Thismessage indicates that the command was unable toobtain storage for more messages. This situation


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai700/cache.htm



occurs only for a long display request, such as a detaildisplay for many group buffer pools.

DSNB499I - DISPLAY TERMINATED DUE TO INSUFFICIENT MESSAGE SPACE

The output is truncated.

To see all of the output, reissue the DISPLAYGROUPBUFFERPOOL command, and specify a smallernumber of group buffer pools.



DSNB751I MVS CFRM POLICY INFORMATIONNOT AVAILABLE FOR GROUPBUFFER POOL gbpname MVSIXCQUERY RETURN CODE =retcode MVS IXCQUERY REASONCODE = reason A PARTIALDISPLAY FOLLOWS

ExplanationThis message is a section of output from the DISPLAYGROUPBUFFERPOOL command, which is part ofmessage “DSNB750I” on page 97.

DSNB752I GROUP DETAIL STATISTICS ARENOT AVAILABLE FOR THE GROUPBUFFER POOL BECAUSE AREBUILD IS IN PROGRESS


DSNB753I GROUP BUFFER POOL STRUCTUREOWNER INFORMATION NOTAVAILABLE IRLM NOTIFY RETURNCODE = retcode IRLM NOTIFYREASON CODE = reason

ExplanationDb2 could not retrieve group buffer pool structureowner information for message DSNB798I becausethe IRLM Notify request did not successfully complete.A preceding DSNB750I or DSNB751I messageidentifies the associated group buffer pool.retcode

Return code from IRLM on the Notify request

reasonReason code from IRLM on the Notify request


Related conceptsIRLM return and reason codes (IRLM)Related informationDSNB750IDISPLAY FOR GROUP BUFFER POOL gbpnameFOLLOWSDSNB751IMVS CFRM POLICY INFORMATION NOTAVAILABLE FOR GROUP BUFFER POOLgbpname MVS IXCQUERY RETURN CODE =retcode MVS IXCQUERY REASON CODE = reasonA PARTIAL DISPLAY FOLLOWS

DSNB755I DB2 GROUP BUFFER POOLSTATUS CONNECTED = status1CURRENT DIRECTORY TO DATARATIO = ratio1 PENDINGDIRECTORY TO DATA RATIO =ratio2 CURRENT GBPCACHEATTRIBUTE = gcache1 PENDINGGBPCACHE ATTRIBUTE = gcache2

ExplanationThis message is a section of output from the DISPLAYGROUP BUFFERPOOL command, which is part ofmessage “DSNB750I” on page 97.

DSNB756I CLASS CASTOUT THRESHOLD =class-threshold1,class-threshold2GROUP BUFFER POOL CASTOUTTHRESHOLD = gbp-threshold %GROUP BUFFER POOLCHECKPOINT INTERVAL = intervalMINUTES RECOVERY STATUS =status1 AUTOMATIC RECOVERY =auto-recovery


DSNB757I MVS CFRM POLICY STATUS FORstructure-name = status2 MAXSIZE INDICATED IN POLICY =psize KB DUPLEX INDICATOR INPOLICY = dupstat CURRENTDUPLEXING MODE = dupmodeALLOCATED = status1




DSNB758I ALLOCATED SIZE = asize KBVOLATILITY STATUS = volstatREBUILD STATUS = rbldstatCFNAME = cfname CFLEVEL -OPERATIONAL = cflevel1 CFLEVEL- ACTUAL = cflevel2


DSNB759I NUMBER OF DIRECTORY ENTRIES= dir# NUMBER OF DATA PAGES =data# NUMBER OF CONNECTIONS= conn#


DSNB760I GBPCACHE OPTION SET TO valueFOR gbpname. IT WILL TAKEEFFECT ON THE NEXTREALLOCATION

ExplanationThis message is issued in response to an ALTERGROUPBUFFERPOOL command that requests achange in the GBPCACHE attribute. It is also issued forthe first ALTER GROUPBUFFERPOOL command for agroup buffer pool, even when the GBPCACHE option isnot specified on the command. (In this case, themessage shows YES for the GBPCACHE option.) Thenew setting takes effect the next time the couplingfacility cache structure is allocated.


System programmer responseUse the MVS command SETXCF START, REBUILDcommand when you are ready for the change to takeeffect.

DSNB761I THE NEW SETTING WILL TAKEEFFECT AFTER THE GBPCACHE

ATTRIBUTE HAS BEEN CHANGEDTO YES

ExplanationThis message is issued in response to an ALTERGROUPBUFFERPOOL command that requests achange to RATIO, CLASST, GBPOOLT or GBPCHKPTwhen GBPCACHE NO is also specified on thecommand or when the current GBPCACHE attribute isNO. The new setting takes effect the next time thecoupling facility cache structure is allocated after theGBPCACHE attribute has been changed to YES.


System programmer responseUse the ALTER GROUPBUFFERPOOL command tochange the GBPCACHE attribute to YES and the MVScommand SETXCF START, REBUILD when you areready for the change to take effect.

DSNB762I DUPLEXING STATISTICS FORsecondary-gbpname WRITESCHANGED PAGES = changed-pagesFAILED DUE TO LACK OF STORAGE= writes-full CHANGED PAGESSNAPSHOT VALUE = changed-pages-snapshot


DSNB763I gbpname IS NOT DEFINED WITHGBPCACHE NO


DSNB764I DUPLEXING STATISTICS FORsecondary-gbpname WRITESFAILED DUE TO LACK OF STORAGE= s2 ASYNC COMPLETION CHECKS= s3



DSNB765I NO CONNLIST REPORT ISGENERATED. THERE ARE NOCONNECTIONS TO THIS GROUPBUFFER POOL.


DSNB766I THE CONNLIST REPORT FOLLOWS


DSNB767I CONNECTION NAME = conname,CONNECTION STATUS = statusCONNECTOR'S RELEASE =connector-release


DSNB768I THERE ARE NO GROUP BUFFERPOOLS DEFINED WITH GBPCACHENO


DSNB769I THE CONNLIST REPORT ISCOMPLETE


DSNB770I MEMBER DETAIL STATISTICS ARENOT AVAILABLE FOR THE GROUPBUFFER POOL. THIS DB2 HASNEVER BEEN CONNECTED TO THEGROUP BUFFER POOL.


DSNB771I INCREMENTAL MEMBER DETAILSTATISTICS SINCE basetime


DSNB772I CUMULATIVE MEMBER DETAILSTATISTICS SINCE basetime


DSNB773I MEMBER DETAIL STATISTICSSYNCHRONOUS READS DUE TOBUFFER INVALIDATION DATARETURNED = r1 DATA NOTRETURNED = r2


DSNB774I DUE TO DATA PAGE NOT INBUFFER POOL DATA RETURNED =r3 DATA NOT RETURNED = r4


DSNB775I PREFETCH READS DATA NOTRETURNED = r5


DSNB776I SYNCHRONOUS WRITESCHANGED PAGES = w1 CLEANPAGES = w2



DSNB777I ASYNCHRONOUS WRITESCHANGED PAGES = changed-pages-count CLEAN PAGES =clean-pages-count FAILED DUE TOLACK OF STORAGE = failed-writes-count WRITE-AROUND PAGES=write-around-count


DSNB778I CASTOUT THRESHOLDSDETECTED FOR CLASSES = t1 FORGROUP BUFFER POOL = t2 GBPCHECKPOINTS TRIGGERED = k1PARTICIPATION IN REBUILD = k2


DSNB780I GROUP DETAIL STATISTICS ARENOT AVAILABLE FOR THE GROUPBUFFER POOL. THIS Db2 IS NOTCURRENTLY CONNECTED TO THEGROUP BUFFER POOL.


DSNB781I GROUP DETAIL STATISTICS ARENOT AVAILABLE FOR THE GROUPBUFFER POOL. MVS IXLCACHERETURN CODE = retcode MVSIXLCACHE REASON CODE = reason


DSNB782I INCREMENTAL GROUP DETAILSTATISTICS SINCE basetime


DSNB783I CUMULATIVE GROUP DETAILSTATISTICS SINCE basetime


DSNB784I GROUP DETAIL STATISTICSREADS DATA RETURNED = r1


DSNB785I DATA NOT RETURNED DIRECTORYENTRY EXISTED = r2 DIRECTORYENTRY CREATED = r3 DIRECTORYENTRY NOT CREATED = r4, r5


DSNB786I WRITES CHANGED PAGES= w1CLEAN PAGES = w2 FAILEDDUE TOLACK OF STORAGE = w3 CHANGEDPAGES SNAPSHOT VALUE= p1


DSNB787I RECLAIMS FOR DIRECTORYENTRIES = d1 FOR DATA ENTRIES= d2 CASTOUTS= c1


DSNB788I CROSS INVALIDATIONS DUE TODIRECTORY RECLAIMS = x1 DUETO WRITES = x2 EXPLICIT = x3



DSNB789I REGISTER PAGE LIST = r7 PAGESRETRIEVED = r8


DSNB790I DISPLAY FOR GROUP BUFFERPOOL gbpname IS COMPLETE


DSNB791I THIS DB2 IS NOT CONNECTED TOgbpname


DSNB792I NO DB2 IN THE GROUP ISCONNECTED TO gbpname


DSNB793I DELETE NAME LIST = s5 READCASTOUT STATISTICS = s6 DELETENAME = s7 OTHERASYNCHRONOUS GBP REQUESTS= s8


DSNB794I THIS DB2 IS NOT CONNECTED TOANY GROUP BUFFER POOL


DSNB795I NO DB2 IN THE GROUP ISCONNECTED TO ANY GROUPBUFFER POOL


DSNB796I CASTOUTS PAGES CASTOUT = c1UNLOCK CASTOUT = c2 READCASTOUT CLASS = c3 READCASTOUT STATISTICS = c4 READDIRECTORY INFO = c5


DSNB797I OTHER INTERACTIONS REGISTERPAGE = o1 UNREGISTER PAGE = o2DELETE NAME = o3 READSTORAGE STATISTICS = o4EXPLICIT CROSS INVALIDATIONS= o5 ASYNCHRONOUS GBPREQUESTS = o6


DSNB798I LAST GROUP BUFFER POOLCHECKPOINT timestamp GBPCHECKPOINT RECOVERY LRSN =lrsn STRUCTURE OWNER =member-name


DSNB799I SECONDARY GBP ATTRIBUTESALLOCATED SIZE = ssize KBVOLATILITY STATUS = svolstatCFNAME = cfname CFLEVEL -OPERATIONAL = cflevel1 CFLEVEL- ACTUAL = cflevel2 NUMBER OFDIRECTORY ENTRIES = sdir#NUMBER OF DATA PAGES = sdata#



DSNB800I DIRECTORY ENTRY TO DATA PAGERATIO SET TO value FOR gbpname.IT WILL TAKE EFFECT ON THENEXT REALLOCATION

ExplanationThis message is issued in response to an ALTERGROUPBUFFERPOOL command that requests achange to the directory entry to the data page ratio fora group buffer pool. It is also issued for the first ALTERGROUPBUFFERPOOL command for a group bufferpool, even when no ratio value is specified on thecommand (in this case, the default ratio value is beingused). The new ratio takes effect the next time thecoupling facility cache structure is allocated.

The directory entry to data page ratio determines thenumber of directory entries and the number of datapages that are allocated in the coupling facility cachestructure for the group buffer pool. If the couplingfacility structure is not allocated, the first connect fromany Db2 causes allocation of the structure and the newdirectory entry to data page ratio to take effect.

If the structure size can be determined from the MVSCFRM administrative policy, message DSNB801I isissued to indicate an estimate of the number ofdirectory and data entries that are allocated based onthe new ratio and the current size of the couplingfacility structure. Otherwise, message DSNB812I isissued.


System programmer responseUse the -DISPLAY GROUPBUFFERPOOL command todisplay the number of allocated directory and dataentries.

DSNB801I MAX STRUCTURE SIZE INDICATEDIN MVS CFRM POLICY = size KBESTIMATED NUMBER OFDIRECTORY ENTRIES = dir#ESTIMATED NUMBER OF DATAPAGES = data#

ExplanationThis message is issued in response to an ALTERGROUPBUFFERPOOL command after the directoryentry to data page ratio is successfully updated. It isalso issued for the first ALTER GROUPBUFFERPOOLcommand for a group buffer pool, even when no ratiovalue is specified on the command (in this case, thedefault ratio value is used). The group buffer pool is

identified in message DSNB800I, which immediatelyprecedes this message.

Because the actual ratio change does not take affectuntil the group buffer pool is reallocated, this messageshows the estimated number of directory entries anddata pages that are allocated based on the new ratioand the maximum size of the coupling facilitystructure, as indicated in the active CFRM policydefinition. The actual number of entries that areallocated varies based on the amount of couplingfacility storage that is available at the time theallocation is attempted, and on the amount of storageoverhead necessary for the coupling facility controlstructures. Because Db2 cannot determine thesevariables, the estimated number of directory and dataentries displayed in this message assumes that theentire storage allocation for the coupling facility cachestructure will be used for directory and data entries,which is not the case.


Related conceptsTuning group buffer pools (Db2 Data SharingPlanning and Administration)Related tasksChanging the ratio of directory to data entries(Db2 Data Sharing Planning and Administration)Related referenceGroup buffer pool monitoring with the DISPLAYGROUPBUFFERPOOL command (Db2 DataSharing Planning and Administration)-ALTER GROUPBUFFERPOOL (Db2) (Db2Commands)-DISPLAY GROUPBUFFERPOOL (Db2) (Db2Commands)Related informationDSNB750IDISPLAY FOR GROUP BUFFER POOL gbpnameFOLLOWSDSNB800IDIRECTORY ENTRY TO DATA PAGE RATIO SETTO value FOR gbpname. IT WILL TAKE EFFECTON THE NEXT REALLOCATION

DSNB802I "value" IS NOT A VALIDPARAMETER FOR 'RATIO'

ExplanationAn illegal value for the RATIO parameter was specifiedfor an ALTER GROUPBUFFERPOOL command. TheRATIO value can be up to 6 characters, and must be adecimal number from 1.0 to 255 (inclusive). For values


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_tuninggroupbps.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_tuninggroupbps.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_changeratiodataentries.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_changeratiodataentries.html








less than 25, any digits after the first decimal place areignored. If the value for the RATIO parameter isgreater than or equal to 25, any digits after thedecimal point are ignored. Informational messageDSNB803I is displayed if the system ignores anyprecision that exceeds the limits of the RATIOparameter.


System programmer responseReissue the ALTER GROUPBUFFERPOOL command,and specify an acceptable value for RATIO.

DSNB803I RATIO IS TRUNCATED TO value

ExplanationThe precision specified on the RATIO parameter on anALTER GROUPBUFFERPOOL command was greaterthan allowed. For decimal numbers less than 25, anydigits after the first decimal place are ignored: forexample, 5.67 is treated as 5.6. For decimal numbersgreater than or equal to 25, any digits after thedecimal point are ignored: for example, 25.3 is treatedas 25.


DSNB804I CLASS CASTOUT THRESHOLD SETTO class-threshold1,class-threshold2 FOR gbp-name

ExplanationThis message is issued in response to an ALTERGROUPBUFFERPOOL command that requests achange to the class castout threshold value for a groupbuffer pool. It is also issued for the first ALTERGROUPBUFFERPOOL command for a group bufferpool, even when no threshold value is specified on thecommand (in this case, the default class castoutthreshold value is used).

class-threshold1The threshold at which class castouts are to beinitiated, expressed as a percentage of the groupbuffer pool size

class-threshold2The threshold at which class castouts are to beinitiated, expressed as an absolute number ofbuffers. class-threshold2 is used to determine thethreshold only if class-threshold1 is zero and class-

threshold2 is non-zero. Otherwise, class-threshold1 is used to determine the threshold.




Related reference-ALTER GROUPBUFFERPOOL (Db2) (Db2Commands)

DSNB805I specified-value IS NOT A VALIDPARAMETER FOR 'CLASST'

ExplanationAn illegal value was specified on the CLASST (class-threshold1,class-threshold2) keyword on an ALTERGROUPBUFFERPOOL command. The class-threshold1value must be an integer between 0 and 90, inclusive.The class-threshold2 value must be an integerbetween 0 and 32767, inclusive.

specified-valueThe specified value for CLASST.


System programmer responseReissue the ALTER GROUPBUFFERPOOL command,specifying an acceptable value for CLASST.

Related reference-ALTER GROUPBUFFERPOOL (Db2) (Db2Commands)

DSNB806I GROUP BUFFER POOL CASTOUTTHRESHOLD SET TO value% FORgbpname

ExplanationThis message is issued in response to an ALTERGROUPBUFFERPOOL command that successfullychanges the group buffer pool castout threshold valuefor a group buffer pool. It is also issued for the firstsuccessful ALTER GROUPBUFFERPOOL command for agroup buffer pool, even when no threshold value isspecified on the command (in this case, the default






group buffer pool castout threshold value is beingused).


DSNB807I value IS NOT A VALID PARAMETERFOR 'GBPOOLT'

ExplanationAn ALTER GROUPBUFFERPOOL command was issuedwith an illegal value specified on the GBPOOLT (groupbuffer pool castout threshold) keyword. The GBPOOLTvalue must be an integer between 0 and 90, inclusive.


System programmer responseReissue the -ALTER GROUPBUFFERPOOL command,specifying an acceptable value for GBPOOLT.

DSNB808I GROUP BUFFER POOLCHECKPOINT INTERVAL SET TOvalue MINUTES FOR gbpname

ExplanationThis message is issued in response to an ALTERGROUPBUFFERPOOL command that successfullychanges the group buffer pool checkpoint intervalvalue for a group buffer pool. It is also issued for thefirst successful ALTER GROUPBUFFERPOOL commandfor a group buffer pool, even when no interval value isspecified on the command (in this case, the defaultgroup buffer pool checkpoint interval value is beingused).


DSNB809I value IS NOT A VALID PARAMETERFOR 'GBPCHKPT'

ExplanationAn ALTER GROUPBUFFERPOOL command was issuedwith an illegal value specified on the GBPCHKPT(group buffer pool checkpoint) keyword. TheGBPCHKPT value must be an integer between 1 and999999, inclusive.


System programmer responseReissue the -ALTER GROUPBUFFERPOOL command,specifying an acceptable value for GBPCHKPT.

DSNB812I SIZE ESTIMATES ARE NOTAVAILABLE FOR THE GROUPBUFFER POOL MVS IXCQUERYRETURN CODE = return code MVSIXCQUERY REASON CODE = reasoncode

ExplanationThe directory entries and data pages estimates for thegroup buffer pool, identified on the precedingDSNB800I message, could not be computed becauseIXCQUERY was unable to obtain the backingstructure's size information from the MVS CFRMadministrative policy definition. This can happen if anIXCQUERY processing error occurred, or if thestructure was not defined in the CFRM policy. Thebacking structure for the group buffer pool must bedefined in the CFRM policy before the group bufferpool can be allocated. The exact reason can bedetermined from the return code and the reason code.For an explanation of the IXCQUERY codes, see z/OSMVS Programming: Sysplex Services Reference.

System actionThe command completes successfully, but withoutgiving the estimates.

DSNB813I csect-name ALTER NOTIFICATIONFAILED

ExplanationAn ALTER GROUPBUFFERPOOL command failed topropagate the request for castout threshold orcheckpoint interval change to other DB2s in the datasharing group. This error is triggered by an errorencountered by the IRLM notification process. As aresult, different DB2s in the group might have differentvalues for the castout threshold or checkpoint interval.The RATIO change does not use the notificationprocess and is, therefore, not affected by such afailure.



System programmer responseReissue the -ALTER GROUPBUFFERPOOL commandwith the same parameters. If the problem persists, itindicates a deeper problem, such as inadequate spacefor the locking structures.

DSNB814I csect-name NO CHANGESREQUESTED ON COMMAND

ExplanationAn ALTER GROUPBUFFERPOOL command without anyparameters was issued for an existing group bufferpool. If an ALTER GROUPBUFFERPOOL commandwithout any parameters is issued for a group bufferpool that does not yet exist, a group buffer pooldefinition with default parameters values is created.

System actionThe command is successful and processing continues.

DSNB815I PAGE P-LOCK LOCK/UNLOCK,REQUESTS FOR SPACE MAP = nnREQUESTS FOR DATA PAGES = nnREQUESTS FOR INDEX LEAF = nnUNLOCK REQUESTS = nn


DSNB816I PAGE P-LOCK SUSPENSIONS/NEGOTIATIONS, SUSPENSIONSFOR SPACE MAP = nn P-LOCKSUSPENSIONS FOR DATA = nn P-LOCK SUSPENSIONS FOR INDEXLEAF = nn NEGOTIATIONS FORSPACE MAP = nn P-LOCKNEGOTIATIONS FOR DATA PAGES= nn NEGITIATIONS FOR INDEXLEAF PAGES = nn


DSNB890I command-verb gbp-kwdCOMMAND IS ONLY VALID FORDATA SHARING

ExplanationAn attempt was made to issue a GROUPBUFFERPOOLcommand on a Db2 that was not initialized toparticipate in data sharing.command-verb

The name of the command attempted: ALTER, orDISPLAY

gbp-kwdThe keyword GROUPBUFFERPOOL or GBPOOL

System actionThe command request is rejected.

DSNB891I name IS NOT A VALID GROUPBUFFER POOL OR COUPLINGFACILITY STRUCTURE NAME

ExplanationAn invalid name was specified on an ALTERGROUPBUFFERPOOL or DISPLAYGROUPBUFFERPOOL command.name

Either the Db2 group buffer pool name or thebacking coupling structure name

You must either specify the Db2 group buffer poolname (gpbname) or the backing coupling facilitystructure name (strname). Acceptable values forgbpname are GBP0, GBP1, ... , GBP49, GBP32K,GBP32K1, ... , GBP32K9. The strname has thefollowing format:

groupname_gbpname

The groupname is the Db2 data sharing group name.The underscore (_) is used as a delimiter between thegroupname and the gbpname.


System programmer responseReissue the command specifying a valid group bufferpool name.

DSNB892I grpname IS NOT A VALID GROUPNAME FOR THIS DB2

ExplanationThe group name specified as part of the full couplingfacility cache structure name on an ALTERGROUPBUFFERPOOL or DISPLAYGROUPBUFFERPOOL command is incorrect. On the


commands, you can specify either the correct 16-bytecoupling facility cache structure name or the Db2group buffer pool name. The coupling facility cachestructure name is a 16-character name specified asfollows:

groupname_gbpname

The gbpname can be GBP0, GBP1, ..., GBP49 GBP32K,GBP32K1, ..., GBP32K9. The groupname is the Db2data sharing group name. The underscore (_) is usedas a delimiter between the groupname and thegbpname. The coupling facility cache structure names

are left-justified with a blank as the rightmost paddingcharacter. Db2 adds the padding blanks if they are notspecified on the command.


System programmer responseReissue the command, specifying a valid group bufferpool name.



Chapter 3. DSNE messagesMessage identifiers that begin with DSNE communicate information about the TSO attachment facility.

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 inthis documentation. If you suspect an error in Db2, you might need to report the problem. For informationabout identifying and reporting the problem, see Collecting diagnostic data (Collecting data).

All DSN command processor trace messages have the same message number: DSNET20I.

DSNET20I

ExplanationThis is one of many possible trace messages bearingthis message number. For information about TSOattachment facility trace messages that have thismessage number, see TSO attachment facility tracemessages (Diagnosing Db2 problems).

DSNE004E PROBABLE SUBSYSTEM ERRORDETECTED IN CSECT csect-name,SUBSYSTEM FUNCTION service,RETCODE retcode, REASON CODEreason-code

ExplanationA subsystem error has occurred. The functionidentified in the message as 'service' is either an MVSor a Db2 service routine. The error was discovered inthe 'csect-name' indicated in the message. Refer to theappropriate MVS publications for a description of thereturn and reason codes.

System actionThis message is sometimes followed by an intentionalsystem abend. In other instances, the DSN commandprocessor will terminate the current subcommand andattempt to continue by issuing another DSN prompt.

User responseRun the job again with a SYSUDUMP dump data setallocated and DSN tracing set to 123. Collect the DSNtrace stream. If an abend occurs, collect the dump.

DSNE005A EXECUTION IS INTERRUPTED.ENTER C TO CANCEL, OR ANYOTHER REPLY TO RESUME THEsubcmd SUBCOMMAND

ExplanationThe Attention key was pressed. Entering a 'C' willcancel the DSN subcommand that is currentlyexecuting. If the user enters a question mark, messageDSNE006A will appear. Any other reply will causeexecution of the subcommand that was in progress tocontinue.

If the DSN prompt was issued just before the Attentionkey was pressed, 'subcmd' may be either 'DSN' or thepreviously invoked subcommand.

User responseEnter a 'C' to cancel the Db2 subcommand currentlyexecuting. The DSN prompt will appear on theterminal. Enter anything else (except anotherattention) to resume execution.

DSNE006A C WILL TERMINATE THESUBCOMMAND WITHUNCOMMITTED CHANGESBACKED OUT

ExplanationEnter a 'C' to terminate the subcommand. Nouncommitted changes are made to the database. Anyother reply causes subcommand execution tocontinue.

User responseEnter a 'C' to terminate the subcommand. Controlreturns to DSN, and the DSN prompt appears on theterminal. This is a second-level help messageassociated with message DSNE005A.

DSNE008I REPLY WAS xxxxx, EXECUTIONRESUMED



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_trbshoottsoattachfacilitytracemessages.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_trbshoottsoattachfacilitytracemessages.html

ExplanationExecution was suspended by a user ATTENTION andthen was resumed, because the string specified in themessage as 'xxxxx' was entered.

System actionControl returns to the interrupted session.

DSNE009I REPLY WAS C, EXECUTIONTERMINATED

ExplanationThe response to message DSNE005A was a C. Thiscaused the current subcommand to terminate.

System actionThe current subcommand is terminated. The DSNprompt appears on the terminal.

User responseYou can now enter another DSN subcommand.

DSNE010I SUBCOMMAND subcmdCANCELED BY ATTENTION

ExplanationThe subcommand specified in the messages wascanceled because the user pressed the attention keyand then entered a 'C'.

System actionThe current subcommand is terminated. The DSNprompt appears on the terminal.

User responseA new subcommand can be entered.

DSNE011I DSN COMMAND CANCELED BYATTENTION

ExplanationThe user of the DSN command processor has pressedattention. Since this occurred before DSN was fullyinitialized, DSN terminates. If DSN had been fullyinitialized, it would have prompted the user tocontinue or cancel.

System actionThe DSN command processor terminates. Controlreturns to TSO or the calling CLIST.

User responseRestart DSN.

DSNE100I ssid NOT OPERATIONAL, RETRYCOUNT IS ZERO

ExplanationThe subsystem (specified in the message as 'ssid') wasnot active, and no retries remain to be executed. Nomore connection attempts are made. The operatorshould be notified to start this specific subsystem, andthe DSN command should be resubmitted. Issue theDSN command with the RETRY parameter set greaterthan zero.

System actionControl returns to TSO.

Operator responseStart the subsystem with the 'ssid' specified in themessage.

User responseNotify the operator to start the subsystem.

DSNE101I ssid NOT OPERATIONAL, WILLRETRY nnn MORE TIMES

ExplanationThe requested Db2 subsystem 'ssid' was not started oris not available. Connection to it will be attempted'nnn' more times. This message is issued every 30seconds (and each time 'nnn' is decreased by 1) untilthe connection is made or 'nnn' is zero.

System actionDSN repeats the connection attempt until theconnection is made or until the retry count isdecreased to zero.

User responseNotify the operator start Db2.

DSNE102I YOU ARE NOT AUTHORIZED TOUSE DB2 SUBSYSTEM ssid

ExplanationThe authorization ID is not authorized to usesubsystem 'ssid'.



User responseContact the system programmer, or systemadministrator to arrange for the required RACF orequivalent security system authorization.

DSNE103E MAIN STORAGE REQUEST FROMcsect-id FAILED

ExplanationA request for main storage failed.

System actionThe TSO attachment facility is ready for more input.

User responseIncrease the address space size. This can be done aspart of the logging on process.

DSNE104E RETRY COUNT OF number NOTVALID, SET TO 120

ExplanationAn invalid 'RETRY' parameter was entered on the DSNcommand. It has been set to 120. Valid retry countsare integer numbers from 0 to 120.

System actionRetry count is modified, and DSN execution continues.

User responseThe next time you invoke DSN, use a RETRY count of 0to 120.

DSNE105E SUBSYSTEM ssid NO LONGEROPERATIONAL

ExplanationThe Db2 subsystem is down. It must be restartedbefore the user can continue.

System actionControl returns to TSO attachment facility.

User responseBefore you can continue, Db2 must be restarted. Youmust also reissue the DSN command. ISPF usersshould restart their jobs.

DSNE106E PLAN plan-id NOT AUTHORIZEDFOR SUBSYSTEM ssid AND AUTH-ID auth-id

ExplanationThe requested combination of plan-id, subsystem-id,and user-id is not currently authorized.


System programmer responseThe system administrator for the Db2 subsystem canarrange the necessary authorization.

User responseNotify the system programmer or system administratorto obtain proper authorization.

DSNE107E SUBSYSTEM RESOURCE NEEDEDFOR PLAN plan-name, AUTH IDauth-id, AND SUBSYSTEM subsysIS NOT AVAILABLE

ExplanationThe Db2 subsystem was unable to allocate anecessary resource for the requested combination ofplan-id, user-id, and subsystem-id. This message isaccompanied by DSNE108E. An attempt to establishconnection with the Db2 subsystem has failed.


User responseArrange to obtain the needed resource, and resubmitthe subcommand. See the explanation for messageDSNE108E, which accompanies this message.

DSNE108E FEEDBACK - REASON CODEreason-code TYPE= resource-typeRESOURCE NAME - resource-name

Chapter 3. DSNE messages 123

ExplanationThis message accompanies message DSNE107E orDSNE114E to explain the problem more clearly.

reason-codeThe reason code for the message.

resource-type and resource-nameThe type and name of the resource that themessage identifies. For an explanation of resource-type and resource-name values, see Appendix C,“Resource types,” on page 1207.


User responseArrange for the missing resource to be available, andresubmit your job.

Related conceptsDb2 reason codes (Db2 Codes)Related informationResource typesType codes are associated with particular typesof resources.DSNE107ESUBSYSTEM RESOURCE NEEDED FOR PLANplan-name, AUTH ID auth-id, AND SUBSYSTEMsubsys IS NOT AVAILABLEDSNE114ETHE COMBINATION OF PLAN planid, AUTH IDauth-id, AND SUBSYSTEM ssid IS NOT VALID

DSNE109E NO INPUT TO BIND,SUBCOMMAND TERMINATED

ExplanationNo LIBRARY parameter was specified on the BINDsubcommand. No DBRMLIB was allocated.


User responseSpecify the LIBRARY parameter, and resubmit theBIND subcommand. Alternatively, you could issue anALLOCATE command for the DDNAME DBRMLIB andthen resubmit the BIND subcommand as originallywritten.

DSNE110E ssid NOT VALID SUBSYSTEM ID,COMMAND TERMINATED

ExplanationThere is no subsystem id with the name identified inthe message as 'ssid'. The subsystem identifier youspecify (or default to) on the DSN command mustexist. This message is the result of specifying (ordefaulting to) a nonexistent subsystem identifier.

System actionThe DSN processor ends, and control returns to TSO.

User responseReissue the command with a valid SYSTEM parameter.

Related conceptsDSN command processor (Db2 Applicationprogramming and SQL)Related referenceDSN (TSO) (Db2 Commands)

DSNE111E INSTALLATION EXIT REJECTEDDSNAME data-set-name

ExplanationA local installation-supplied exit has rejected the dataset name identified in the message as 'data-set-name'.


User responseEither correct the data set name specified, or arrangeto authorize the original data set name. Resubmit therequest.

DSNE112E userid STILL SIGNED ON TOSUBSYSTEM ssid

ExplanationAn attempt was made to sign on to Db2 when the userwas already signed on.


User responseLog off and log on again.

DSNE113E NOT ABLE TO LINK TO PROGRAMprogram-name IN DSNAMEdataset-name.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_dsncommandprocessor.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_dsncommandprocessor.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_dsn.html

ExplanationA TSO attachment error occurred during an attempt tolink to program program-name in data set dataset-name.

program-nameThe name of the program.



User responseCheck that the program exists and that its name isspelled correctly. Enter the correct program name.

DSNE114E THE COMBINATION OF PLANplanid, AUTH ID auth-id, ANDSUBSYSTEM ssid IS NOT VALID

ExplanationThe resource in message DSNE108E, which will followthis message, is not a valid resource name.


User responseCorrect the invalid combination, and resubmit thesubcommand. The problem is probably caused by auser spelling error. If it is not, check with the systemadministrator to determine the availability of theneeded resource. Your program may need to bebound. See the explanation for message DSNE108(which accompanies this one) for more information.

DSNE117E NOT ABLE TO LOCATEmembername IN DSNAME data-set-name

ExplanationThe 'data-set-name' specified does not contain themember the user wanted to run.

System actionControl remains with the DSN command processor,and the DSN prompt appears on the terminal. The DSNcommand processor is ready for another command.

User responseCorrect the PROGRAM or LIBRARY parameter, andresubmit the subcommand.

DSNE118E invalid-command NOT VALIDCOMMAND

ExplanationThe user entered an invalid command. A typing errormay be responsible. You may be trying to run acommand processor that is either not available on yoursystem or that is not part of your current LNKLST orSTEPLIB concatenation.


User responseEither correct the spelling error, or rearrange yourlibrary concatenation so that you can access therequired command processor. Resubmit thecommand.

DSNE119E data-set-name NOT PARTITIONEDDATA SET

ExplanationThe user tried to allocate a sequential data set when apartitioned data set was required.


User responseCheck the data-set-name. The data set you specified issequential, but you specified a member name. Removethe member name, and resubmit the job.

DSNE120E data-set-name NOT SEQUENTIALDATA SET

ExplanationThe user tried to allocate a partitioned data set when asequential data set was required.



User responseCheck the data-set-name. The data set you specified ispartitioned, but you did not specify a member name.Add a member name, and resubmit the job.

DSNE121E csect-id NOT ABLE TO OPEN DATASET

ExplanationThe Db2 subsystem was unable to open the requesteddata set.


User responseFor information about why the data set could not beopened, read the explanations of the messages thataccompany this message. Correct the condition, andresubmit the job.

DSNE122E DATA SET ORGANIZATION MUSTBE EITHER SEQUENTIAL ORPARTITIONED. data-set-name ISNOT

ExplanationThe Db2 subsystem was unable to open data set 'data-set-name', because it is not a sequential or partitioneddata set.


User responseCorrect the data-set-name, or change the data setorganization. Resubmit the job.

DSNE123I data-set-name NOT PARTITIONEDDATA SET, IT IS IGNORED

ExplanationThe data-set-named in the message is required to bepartitioned. It is not and, consequently, was ignored.

System actionDSN will attempt to continue BIND processing.

User responseCorrect the subcommand, and resubmit it.

DSNE124E DATA SET data-set-name, MEMBERmember-name IN USE, TRY LATER

ExplanationThe member contained in 'data-set-name' is currentlyin use. This message is normally issued when anotheruser is updating the specified member.


User responseWait until the member is available and reissue yourDCLGEN request.

DSNE125E DATA SET data-set-name IN USE,TRY LATER

ExplanationThe sequential data set 'data-set-name' is currently inuse. This message is normally issued when anotheruser is updating the specified data set.


User responseWait until the data set is available and reissue yourDCLGEN request.

DSNE126E THE DB2 OPERATOR IS STOPPINGTHE SUBSYSTEM. PLEASE ENDYOUR DSN SESSION

ExplanationThe operator has requested that Db2 quiesce. Theuser should promptly finish the current task andterminate the DSN session so that this can take place.This message may be followed by message DSNE127I.

System actionNo new users will be permitted to initiate Db2sessions. Current users will be permitted to work untilthey terminate their connections to Db2.

User responseEnd your DSN session as soon as possible.


DSNE127I THE DB2 OPERATOR IS STOPPINGTHE SUBSYSTEM. DSN ISTERMINATING

ExplanationThe operator has requested that Db2 terminate.

System actionDb2 will shut down, interrupting user activities asnecessary. DSN will terminate immediately and returnthe user to TSO.

User responseReinitiate your session when Db2 returns.

DSNE128I DB2 IS ABNORMALLY ENDING.DSN IS TERMINATING

ExplanationDb2 has encountered a problem from which it cannotrecover.

System actionDb2 is abending. DSN terminates immediately andreturns the user to TSO.

User responseReinitiate your session when Db2 returns.

DSNE130I MAXIMUM NUMBER OF DB2USERS REACHED. YOUR RETRYCOUNT IS ZERO

ExplanationThe number of concurrent connections to Db2 isrestricted. The number is specified in the installationparameters in member DSN6SYSP. For TSOforeground, see parameter IDFORE. For backgroundjobs, see parameter IDBACK. The DSN request hasbeen denied, because the current number of Db2connections in the system has reached theinstallation-specified limit.


User responseResubmit the DSN command when activity using Db2has diminished. If still unsuccessful, see the systemprogrammer about the installation parameters.

DSNE131I MAXIMUM NUMBER OF DB2USERS REACHED. WILL RETRYnnn MORE TIMES

ExplanationThe number of concurrent connections to Db2 isrestricted. The number is specified in the installationparameters in member DSN6SYSP. For TSOforeground, see the value of the IDFORE subsystemparameter. For background jobs, see the value of theIDBACK subsystem parameter. The DSN request wasdenied because the current number of Db2connections in the system reached the installationspecified limit.

The DSN connection to Db2 is attempted nnn moretimes. The number of retries is determined by theRETRY parameter on the DSN command.

This message is issued every 30 seconds (and eachtime nnn is decreased by 1) until the connection ismade or until nnn is decreased to zero.

System actionDSN repeats the connection attempt until theconnection is made or the retry count is decreased to0.

User responseIf all retry attempts fail, resubmit the DSN commandwhen Db2 activity diminishes. If still unsuccessful, seethe system programmer about the installationparameters.

Related tasksSetting thread limits (Db2 Performance)Setting TSO options for threads (Db2Performance)Related referenceDSN (TSO) (Db2 Commands)MAX TSO CONNECT field (IDFORE subsystemparameter) (Db2 Installation and Migration)MAX BATCH CONNECT field (IDBACKsubsystem parameter) (Db2 Installation andMigration)Related informationAbout Db2 and related commands (Db2Commands)

DSNE132I DB2 IS OPERATING INRESTRICTED ACCESS MODE.MAINTENANCE PERSONNEL ONLY


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_setthreadlimits.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_settsooption4threads.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_settsooption4threads.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_dsn.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_idfore.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_idfore.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_idback.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_commanddescriptions.html


ExplanationDb2 is not available for normal operation. It is onlyavailable to service personnel.

System actionControl returns to the caller. Your request was notprocessed. The DSN command processor was unableto connect to Db2.

User responseWait until Db2 is available for general use, thenresubmit your request.

DSNE133E csect-name RELEASE LEVELS NOTCOMPATIBLE. DSN=release_level,DB2=release_level

ExplanationThe DSN command processor, perhaps running underthe control of DB2I, has detected a release levelincompatibility between itself and Db2. The currentrelease_level of the DSN command processor code andthe Db2 subsystem load modules is indicated as astring of three numeric characters as follows:

• Version• Release• Modification level

System actionThe DSN command processor terminates.


System programmer responseIf you are unable to determine the problem, you cantrace DSN execution through DB2I or the DSNcommand processor.

User responseCheck that your method of invoking DSN or DB2Iallocates the correct libraries for DSN. If you used JCLor a TSO logon procedure to execute DSN code, checkyour JOBLIB and STEPLIB allocations. If you used aCLIST to execute DSN, ensure that you obtained thecorrect version of the DSN code. See your systemprogrammer if you invoke DSN using proceduressupplied by your system programmer.

Problem determinationEnsure that coexistence is supported on both releaselevels (DSN and Db2). If coexistence is supported,ensure that the lower level release has the correct SPElevel code support that is required to coexist with thecurrent higher level release.

For more information about coexistence and SPEs,refer to the program directory or preventative serviceplanning (PSP) updates.

DSNE136I DB2 IS OPERATING IN RESTARTLIGHT MODE. INDOUBTRESOLUTION ONLY

ExplanationThe Db2 member is not available for normal operation.It is only available to commit coordinators that haveindoubt units of recovery that need to be resolved withthis member.

System actionControl returns to the caller. Your request was notprocessed. The DSN command processor was unableto connect to Db2.

User responseWait until this Db2 is available for general use, thenresubmit your request. Or, request connection to adifferent Db2 member in the data sharing group (forexample, by using the Db2 group attach name).

DSNE137I YOU ARE NOT AUTHORIZED TOCONNECT TO DB2 ASUSER userid.

ExplanationThe authorization ID is not authorized to use Db2 withthe ASUSER userid.

System actionThe request was not processed.

User responseContact the system administrator to arrange for therequired trusted context authorization.

DSNE138E NOT ABLE TO LINK TO PROGRAMprogram-name IN THE STANDARDSEARCH ORDER. RETURN CODEreturn-code. REASON CODEreason-code.


ExplanationA Db2 TSO attachment error occurred during anattempt to link to program program-name using thestandard load module search order.program-name

The name of the program.reason-code

The Db2 reason code value that indicates thereason for the failure. For explanations of reasoncodes, see Db2 reason codes (Db2 Codes).

reason-codeThe reason for the message or SQL code, indicatedby one of the following values:

System action:The TSO attachment facility is ready for more input.

User response:Correct the program or execution environment, andresubmit the subcommand.

DSNE139E NOT ABLE TO LINK TO MEMBERmember-name IN THE STANDARDSEARCH ORDER.

ExplanationThe member member-name was not found using thestandard load module search order.member-name

The member name of a particular Db2 subsystemin a data sharing group.

System action:Control remains with the DSN command processor,and the terminal displays the DSN command prompt.The DSN command processor is ready for anothercommand.

User response:Correct the program or execution environment, andresubmit the subcommand.

DSNE140I THE MAXIMUM NUMBER OFSESSIONS HAS BEEN REACHED.YOU WILL NOT BE CONNECTED TODB2.

ExplanationThe authorization ID has exceeded the maximumnumber of concurrent sessions allowed.

System actionThe connection request is not processed.

User responseAsk the system administrator to increase the numberof concurrent sessions allowed or to close some of theexisting connections, then try the request again.

DSNE231A ONE NAME IS REQUIRED TO FREEA PLAN OR A PACKAGE

ExplanationThe user has attempted to use the FREE PLAN orPACKAGE panel without specifying a plan or packagename.


User responseEnter the name of a plan or package, or (*) to indicate'all'.

DSNE232A CONNECTION NAME REQUIRESENABLE/DISABLE OFCONNECTION TYPE

ExplanationThe user indicated that specific connection nameswere to be specified for ENABLE or DISABLE, but theassociated connection type field was not updated. TheENABLE or DISABLE of connection names requires thecorresponding connection type to also be specified forENABLE or DISABLE.


User responseEnter Y (Yes) on the connection type for the associatedconnection names.

DSNE233A MEMBER NAME MUST NOT BESPECIFIED MORE THAN ONCE

ExplanationThe LIBRARY field containing the data set name, alsocontains a member name.




User responseThe member name must be specified only once, andmust be specified on the MEMBER field.

DSNE234A EITHER DBRM MEMBER ORINCLUDE PACKAGE LIST MUST BESPECIFIED

ExplanationThe BIND PLAN subcommand requires either a DBRMmember name or a package list as input, neither wasspecified.


User responseEnter a DBRM member name(s), or specify that apackage list is to be included. Both options are alsoallowed.

DSNE235A plan/package NAME IS ADUPLICATE OF PRIMARY plan/package NAME

ExplanationIn addition to the primary 'plan' or 'package' namespecified on the REBIND or FREE subcommand panel,the user also specified that additional plans orpackages were to be included in the list. The primary'plan' or 'package' name was again specified to beincluded in the list.

System actionThe duplicate of the primary 'plan' or 'package' nameis automatically deleted from the list to avoid errorsduring subcommand processing. The TSO attachmentfacility is ready for more input.

User responseComplete the list of additional plans or packages.

DSNE236A SPECIFY A CONNECTION TYPE TOENABLE OR DISABLE

ExplanationThe user indicated that individual connection typeswere to be ENABLED or DISABLED, but no specificconnection types were specified.


User responseEnter Y (YES) for each individual connection type toENABLE, or DISABLE.

DSNE237A SPECIFY ENABLE ALL ORSPECIFIC CONNECTION TYPES

ExplanationIn addition to requesting that all connection types beenabled, the user also requested that specificconnection types be enabled. The enable of allconnection types includes the enable of specificconnection types.


User responseSpecify specific connection types to be enabled, orspecify that all connection types are to be enabled.

DSNE240A ISPF RETURNED AN UNEXPECTEDCODE WHILE CLOSING A TABLE

ExplanationAn ISPF error return code was encountered whenattempting to perform a TBCLOSE for an ISPF tablewhile processing the current subcommand panel.

System actionTSO processing for the current subcommand isterminated.

System programmer responseVerify that the ISPF table library allocated to theDSNETBLS DD statement has sufficient space ordirectory entries available. Also refer to the ISPF errorlog for additional diagnostic information.


DSNE241A INTERNAL PROCEDURE WASPASSED AN INVALID NUMBER OFARGUMENTS


ExplanationA TSO Interpreter error was encountered whileexecuting a subroutine during the processing of thecurrent subcommand.


System programmer responseNotify IBM Support that an error was encountered inthe TSO SYSCALL instruction.


Problem determinationThe TSO SYSCALL instruction is not passing all theparameters to a subroutine defined within the CLIST.

DSNE242A ISPF RETURNED AN UNEXPECTEDCODE WHILE SETTING SEARCHARGUMENTS

ExplanationAn ISPF table for the current function does not containthe expected column or table format.


System programmer responseDelete the ISPF table in error. The table is re-createdautomatically during the next invocation of the DB2Ifunction.


Problem determinationThe format of the ISPF table was changed since thelast successful use of the table. Refer to the DB2I ISPFtable library allocated to the DSNETBLS DD statement,and examine the ISPF error log for additionaldiagnostic information.

DSNE243A ISPF RETURNED AN UNEXPECTEDCODE DURING A TABLE DISPLAY

ExplanationAn ISPF error was encountered when attempting todisplay a DB2I table panel.


System programmer responseEnsure that the DB2I panel and panel library areestablished correctly. If the format of both is correct,use ISPF option 7.2 to test the panel for additionalerrors.

Examine the ISPF error log for additional errorinformation and determine the name of the panel to bedisplayed.


DSNE244A CANNOT SAVE CREATED TABLE,VERIFY SPACE IN TABLE LIBRARY

ExplanationAn ISPF TBSAVE function returned with a conditioncode greater than zero.


System programmer responseVerify that the ISPF table library allocated to theDSNETBLS DD statement has sufficient space anddirectory entries available. Also refer to the ISPF errorlog for additional diagnostic information.


DSNE245A ISPF RETURNED AN UNEXPECTEDCODE WHILE ADDING A ROW TO ATABLE

ExplanationAn ISPF TBADD function returned with a conditioncode greater than four.



System programmer responseVerify that the user has enough memory to performISPF functions. Also refer to the ISPF error log foradditional diagnostic information.

User responseEnter the DB2I CANCEL command, and notify thesystem programmer.

DSNE246A ISPF RETURNED AN UNEXPECTEDCODE WHILE DELETING A ROW

ExplanationAn ISPF TBDELETE function returned with a conditioncode greater than zero.


System programmer responseVerify that the user has enough memory to performISPF functions. Also refer to the ISPF error log foradditional diagnostic information.


DSNE247A ISPF RETURNED AN UNEXPECTEDCODE WHILE UPDATING A ROW

ExplanationAn ISPF TBPUT function returned with a conditioncode greater than four.


System programmer responseVerify that the user has enough memory to performISPF functions. Recreate the user actions that lead tothe failure. Also refer to the ISPF error log foradditional diagnostic information.


DSNE248A COMMAND ENTERED CONTAINSINVALID CHARACTERS,RESPECIFY

ExplanationThe command entered at the command line containsan invalid character, the command must be reentered.


User responseCorrect the invalid command entry.

DSNE250A PLEASE ENTER THE COMMAND ATTHE LINE WITH THE PLAN/PACKAGE NAME

ExplanationSELECT or RESET commands must be entered on theline where the plan or package name is shown. Thisline contains the name of the plan or package, whilethe secondary lines do not.

System actionThe line command is rejected. The TSO attachmentfacility is ready for more input.

User responseReenter the line command on the primary plan orpackagelines.

DSNE252A JCL WAS NOT CREATED, ERRORerrcode WHILE DOINGfunction_name FUNCTION

ExplanationError code 'errcode' was received while doing afunction 'function_name', the JCL was not created.

System actionRefer to z/OS ISPF Dialog Developer's Guide for thecause of this error.

User responseContact your systems programmer.


Problem determinationUse the return code/function combination to find thecauses for the problem in z/OS ISPF Dialog Developer'sGuide and correct the problem.


• Listing of the ISPF log for the session involved in theproblem.

Severity20

DSNE283A THE , (COMMA) OPTION ISINCOMPATIBLE WITH THEhostlang LANGUAGE

ExplanationThe user tried to select the 'hostlang' APPLICATIONLANGUAGE and the comma option of the DECIMALPOINT field on the DB2I defaults panel. Thiscombination is not supported.

System actionThe defaults panel is displayed again.

User responseEither change the APPLICATION LANGUAGE field orthe DECIMAL POINT field. If you need the C (C/370Compiler), then the DECIMAL POINT field mustcontain a decimal point (.).

DSNE288A YOU CANNOT SPECIFY (RUN)=YESWITH CICS OR IMS

ExplanationApplication programs that make CICS or IMS callscannot be run from the TSO environment. They can,however, be precompiled, bound, compiled, and linkedunder TSO. The user should specify N on the RUNpanel when preparing a CICS or IMS application.

System actionThe system is waiting for new input to the panel.

User responseChange the RUN option to N.

DSNE291A ALL DB2 COMMANDS BEGIN WITHA DASH

ExplanationThe user omitted the Db2 command recognitioncharacter that must precede all Db2 commands.

System actionThe Db2 commands panel is displayed again so theuser can resubmit the command.

User responseAdd the Db2 command recognition character, andreenter the command.

DSNE292I DATA SET data-set-name NOWCONTAINS YOUR JCL

ExplanationDB2I has just created some JCL for you. The JCL nowresides in data set 'data-set-name'. You can now editthis data. The TSO SUBMIT command will start the jobrunning in background.

System actionThe system is waiting for your next request.

User responseYou can start another DB2I job or leave the panel.

DSNE293A MEMBER NAME IS REQUIRED.YOUR PROGRAM MUST BE IN APDS

ExplanationThe user either has attempted to run a program that isnot in a partitioned data set or has forgotten to specifya member name.

System actionThe RUN panel will be displayed so that the user canspecify a member name and try the run again.

User responseSpecify a member name, and rerun the program.

DSNE294I SYSTEM RETCODE=hex-code USEROR DSN RETCODE=decimal-code

ExplanationA DB2I function has just completed. The return codesfor that function are returned in this message. Thevariable 'hex-code' is a 3-digit hexadecimal number;


the variable 'decimal-code' is a 3-digit decimalnumber. Refer to the appropriate MVS publication forexplanations of the return codes.

System actionDB2I is ready for another execution cycle unless othermessages appeared indicating that Db2 is unavailable.

User responseYou may have to change input parameters to correctunsatisfactory completion codes.

DSNE295A YOU CANNOT DISPLAY ANDRESTART A UTILITY AT THE SAMETIME

ExplanationYou have set options on the DB2I Utilities panel thatcall for conflicting actions. You can either DISPLAY thestatus of a utility, or you can RESTART a utility, but youcannot do both.


User responseEither change the RESTART option to NO, or select adifferent FUNCTION.

DSNE296A YOU CANNOT TERMINATE ANDRESTART A UTILITY AT THE SAMETIME

ExplanationYou have set conflicting options on the DB2I Utilitiespanel. You can either TERMINATE a utility, or you canRESTART a utility, but you cannot do both.


User responseEither change the RESTART option to NO, or select adifferent FUNCTION.

DSNE297A ENTER DATA SET NAME: COPYDSNOR RCPYDSN1

ExplanationYou have not specified a data set name for the COPYutility. A data set name for the local/current site(COPYDSN), and/or the recovery site (RCPYDSN1) isrequired.


User responseEnter a data set name for COPYDSN, and/orRCPYDSN1.

DSNE298A ERROR DURING EDIT: CLIST dataset name

ExplanationErrors were encountered while attempting to changethe online book data set names in the Db2 CLISTmember DSNEMC01. No data set names werechanged.


System programmer responseIf you are unable to determine the problem, you cantrace the Db2 CLIST execution while displaying thispanel.

User responseEnsure that the CLIST data set name is correct andcontains the DSNEMC01 CLIST member to bechanged. This CLIST data set must also be available tothe TSO user ID in WRITE mode. This error willcontinue to be displayed on the panel until the error isresolved or the user exits the panel (END).

Problem determinationExamine the CLIST trace output for any TSO/ISPFnonzero return codes encountered during CLISTexecution.

If you suspect an error in Db2, you might need toreport the problem. For information about identifyingand reporting the problem, see Collecting diagnosticdata (Collecting data).

DSNE340I INTERNAL ERROR - ILLEGAL TYPEIN MODULE module-name




ExplanationAn internal Db2 problem has occurred. The namedmodule has detected a nonexistent SQLTYPE.

System programmer responseIf you suspect an error in Db2, you might need toreport the problem. For information about identifyingand reporting the problem, see Collecting diagnosticdata (Collecting data).

User responseCollect the SPUFI trace and ISPF log, and notify eitherthe system programmer or the database administrator.

You may have to rerun the failing job after you haveturned on trace. This will enable you to send tracemessages to the ISPF log.

DSNE345I WARNING: DB2 DATACORRUPTION CAN RESULT FROMTHIS SPUFI SESSION BECAUSETHE CCSID USED BY THETERMINAL IS NOT THE SAME ASTHE CCSID USED BY SPUFI.TERMINAL CCSID terminal-ccsid.SPUFI CCSID: spufi-ccsid. NOTIFYTHE DB2 SYSTEMADMINISTRATOR.

ExplanationThe current SPUFI session was initiated on a TSOterminal that uses a coded character set identifier(CCSID) of terminal-ccsid. However, SPUFI was boundon the local Db2 server using a CCSID of spufi-ccsid.This discrepancy can lead to unexpected dataconversion, affecting any characters that do not mapto the same code point in the two CCSIDs.

If terminal-ccsid is blank, then the terminal code pageand character set cannot be queried or they are notsupported by ISPF. Possible reasons why the terminalcode page and character set cannot be queriedinclude:

• Hardware limitation such as use of older terminals• Improper configuration of the terminal emulator

software• Improper BTAM or control unit setup

A blank spufi-ccsid indicates that SPUFI might havereceived an unexpected SQLCODE when it attemptedto query the current application encoding scheme.Diagnostics for that SQLCODE appear directly after theDSNE345I message in the message warning panel.

System actionSPUFI waits for the user to indicate whether tocontinue or quit.

System programmer responseOn the local Db2, SPUFI expects to process onlyEBCDIC character data encoded in the CCSID of spufi-ccsid. Ensure that the user's TSO terminalconfiguration is updated to use a CCSID of spufi-ccsid.Verify the data integrity of all tables modified duringthe SPUFI session and follow standard recoveryprocedures. Contact IBM for guidance if widespread orlong term data corruption is evident (for example, ifmany users report this message when using SPUFI).

Special considerations:Blank CCSIDs

As noted previously, a blank terminal-ccsid settingoccurs when the terminal code page and characterset cannot be queried or they are not supported byISPF. Check for the following situations:

• If the message occurs when using a terminalemulator, verify that the emulator software isconfigured with a CCSID setting.

• Check the VTAM® setup: The VTAM logmodeentry used to define the session characteristicsfor the terminal must have the EDS (extendeddata stream) bit turned 'on' in the PSERVIC (thatis, pservic=xx80xx..). For more information,consult z/OS ISPF Planning and Customizing andthe z/OS SNA Network Implementation Guide.

• Older terminal hardware such as the IBM 327xseries do not support the EDS, so a CCSIDcannot be determined. You can instruct users ofsuch devices to specify in the SPUFI defaultspanel that the DSNE345I message should besuppressed. Note that suppression applies onlywhen the terminal CCSID is blank. You cannotuse this field to suppress DSNE345I whenterminal-ccsid is non-blank.

A blank spufi-ccsid indicates that SPUFI probablyreceived an unexpected SQLCODE when it attemptedto query the current application encoding scheme.Check the diagnostics for the SQLCODE that isdisplayed directly after the DSNE345I message, andthen respond to the diagnostics accordingly.

User responseNotify the system programmer. Depress the END keyto quit or the ENTER key to continue. Important:Continuing can result in corruption of data stored byDb2.




Related tasksMaking SPUFI work with different terminalCCSIDs (Db2 Installation and Migration)

DSNE346I WARNING: ALL SHIFT-IN ANDSHIFT-OUT CHARACTERS IN THE'FOR BIT DATA' COLUMNS IN THEOUTPUT ABOVE HAVE BEENREPLACED BY THE SUBSTITUTIONCHARACTER '.'

ExplanationThe current SQL query returned one or more columnsthat have a data type of CHAR FOR BIT DATA,VARCHAR FOR BIT DATA, or both. Also, the currentSPUFI session indicates that a graphic character set isbeing used. To prevent the possible corruption ofoutputted data elsewhere in the report, all shift-in(code point x'0E') and shift-out (code point x'0F')characters will be replaced with a substitutioncharacter of '.' (code point x'4B').

System actionSPUFI processing continues.

User responseTo avoid the substitution character for shift-in andshift-out data, and in order to see all FOR BIT DATA inhexadecimal format, go to the SPUFI defaults paneland change the setting of the FOR BIT DATA field fromASIS to HEX.

DSNE351A EDIT PROCESSING OPTION MUSTBE Y (YES) OR N (NO)

ExplanationThe user specified an edit option other than 'YES', 'NO',or the abbreviation 'Y' or 'N'. A valid user responsedetermines whether SPUFI invokes the ISPF editor toallow the user to edit the input data set.

System actionSPUFI will wait until the user enters a valid response.

User responseType in a 'Y' or an 'N', and press 'ENTER'.

DSNE352A EXECUTE PROCESSING OPTIONMUST BE Y (YES) OR N (NO)

ExplanationThe user specified an execute option other than 'YES','NO', or the abbreviation 'Y' or 'N'. A valid userresponse determines whether SPUFI executes the SQLstatements in the user input data set.

System actionSPUFI waits until the user enters a valid response.


DSNE353A BROWSE PROCESSING OPTIONMUST BE Y (YES) OR N (NO)

ExplanationThe user specified a browse option other than 'YES','NO', or the abbreviation 'Y' or 'N'. A valid userresponse determines whether SPUFI invokes ISPFBROWSE to allow the user to browse the output dataset.

System actionSPUFI will wait until the user enters a valid response.


DSNE354A AUTOCOMMIT PROCESSINGOPTION MUST BE Y (YES) OR N(NO)

ExplanationThe user specified an AUTOCOMMIT option other than'YES', 'NO', or the abbreviation 'Y' or 'N'. A valid userresponse determines whether SPUFI automaticallycommits all the changes to the database subsystem.This was encountered as a result of executing theuser’s SQL statement(s). The commit is done at theend of the processing of an input data set, if it isrequested and if there has been no SQL executionerror.




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_makespufiworkwccsids.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_makespufiworkwccsids.html

DSNE355A CHANGE DEFAULTS PROCESSINGOPTION MUST BE Y (YES) OR N(NO)

ExplanationThe user specified a change-default option other than'YES', 'NO', or the abbreviation 'Y' or 'N'. A valid userresponse determines whether SPUFI displays thecurrent-session SPUFI defaults and allows the user tochange the defaults.



DSNE359A OUTPUT DATA SET NAMEREQUIRED FOR EXECUTE ORBROWSE

ExplanationThe user did not specify the name of the output dataset.

System actionSPUFI waits until the user specifies an output data set.

User responseType in the correct entry, and press 'ENTER'.

DSNE360A THE OUTPUT DATA SET MUSTRESIDE ON DASD

ExplanationThe user has attempted to send the output of SPUFI toa SYSOUT data set. He must enter a generic deviceclass that contains only DASD devices.

System actionSPUFI waits until the user specifies a valid outputdevice class.


DSNE361I SPUFI PROCESSING COMPLETE

ExplanationThis informational message is displayed after SPUFIsuccessfully created the output data set. If errors areencountered before the completion of output data setprocessing, or during the subsequent BROUSEOUTPUT option for this data set, this message isreplaced by either SPUFI or TSO/ISPF error messages.

System actionThe system waits for the next user input.

User responseAt this point you can change the SPUFI panel variablesettings to initiate a new SPUFI request, or you canexit SPUFI.

DSNE363A ONLY RR (REPEATABLE READ), CS(CURSOR STABILITY), OR UR(UNCOMMITTED READ) ALLOWED

ExplanationThe user has entered an invalid isolation level. Thisvalue must be one of the following:

• RR• CS

'Isolation level' here refers to the degree to which theSPUFI user wants to isolate SQL execution from theeffects of other concurrently executing Db2applications.

RR

If the repeatable read (RR) level is specified andthe AUTOCOMMIT option is 'YES', otherapplications can modify the selected databasevalues as soon as the SPUFI EXECUTE phase iscompleted and as soon as the automatic COMMIT(or ROLLBACK, if an error was encountered)operation is performed. Therefore, it is possiblethat the retrieved data being browsed by the userhas already been modified by another application.

If the RR level is specified and the AUTOCOMMIToption is 'NO', then no other Db2 applicationexecuting concurrently can change any of theselected database values until the SPUFI userissues either a COMMIT or a ROLLBACK. Therefore,other applications might be in a normal wait statewhile the SPUFI user is browsing the output dataset.

CS

If the cursor stability (CS) level is specified, it doesnot make any difference whether theAUTOCOMMIT option is 'YES' or 'NO'. Other


concurrently executing Db2 applications canchange the selected database values as soon asthe SELECT has completed.

UR

If the uncommitted read (UR) level is specified,SPUFI queries can read data that has beenchanged, but has not yet been committed byanother application. It does not make anydifference whether the AUTOCOMMIT option is'YES' or 'NO'. Other concurrently executing Db2applications can change the selected databasevalues without waiting for the SELECT to complete.

System actionSPUFI waits until the user specifies a valid isolationlevel.


DSNE364A token IS INVALID AS AN SQLSTATEMENT TERMINATOR

ExplanationThe user has entered an SQL statement terminator(token) that is not supported. The following values arenot valid for use as a SQL statement terminator:

• blank• comma• single and double quotes• underscore• left and right parenthesis

System actionThe statement cannot be executed.

User responseSpecify a valid SQL statement terminator.

DSNE365A SQL STATEMENT TERMINATORHAS BEEN CHANGED TO token

ExplanationThe SPUFI input data set contains a #SET statementthat changes the SQL statement terminator to token.

System actiontoken is the SQL statement terminator until another#SET statement changes it or the end of the input datais reached.

DSNE366A ONLY THE LISTED RECFM TYPESARE ALLOWED

ExplanationThe user has entered an invalid record format for theoutput data set.

System actionThe system waits until the user enters one of theallowed RECFM types.

User responseEnter a RECFM of V, VB, VBA, F, FB, or FBA.

DSNE367A ACTION MUST BE C (COMMIT) ORR (ROLLBACK) OR D (DEFER)

ExplanationThis message requests the user to make a commitaction decision.

User responseTo commit all the changes made since the last commitpoint, enter a 'C'. To undo all the changes that havebeen made since the last commit point, enter an 'R'. Todefer the decision, enter a blank.

DSNE368A YES OR NO MUST BE ENTEREDFOR EACH PROCESSING OPTION

ExplanationOne of the processing options was left blank or set toblank by the user.

User responseEnter 'YES' or 'NO' for each processing option.

DSNE370A INPUT DATA SET COULD NOT BEOPENED

ExplanationThe input data set could not be opened because ofinvalid data set attributes. The logical record length(LRECL) of the input data set must be 80K. The recordformat (RECFM) must be either F or FB. The input dataset may be either sequential or partitioned.


User responseSpecify an input data set having valid attributes.

DSNE371A OUTPUT DATA SET COULD NOT BEOPENED

ExplanationThe output data set could not be opened because ofinvalid 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 VBA. The output data set must be sequential.

User responseEither specify an output data set having validattributes, or enter correct attributes for this data set.

DSNE372A OUTPUT DATA SET MUST BESEQUENTIAL

ExplanationThe user has requested that a nonsequential outputdata set contain the output from execution of SQLstatements.

User responseEnter the data-set-name of a sequential data set forthe output data set.

DSNE374A OUTPUT DATA SET MUST BESEQUENTIAL

ExplanationThe output data set is of unrecognized organization. Itmust be sequential.

System actionProcessing does not begin until the panel entries arecorrect and the user presses 'ENTER'.

User responseThe output data set must be sequential. Enter asequential data-set-name (no member) in the outputdata set field.

DSNE375A ACCESS TO INPUT DATA SET NOTAUTHORIZED

ExplanationA local installation-supplied exit has rejected access tothe input data set specified by the user.

User responseEither specify the name of a data set for whichauthorization will be allowed, or arrange to authorizethe original data-set-name. Resubmit the request.

DSNE376A ACCESS TO OUTPUT DATA SETNOT AUTHORIZED

ExplanationA local installation-supplied exit has rejected access tothe output data set.

User responseEither specify the name of a data set for whichauthorization will be allowed, or arrange to authorizethe original data-set-name. Resubmit the request.

DSNE377A INPUT DATA SET RECFM MUST BEF OR FB WITH LRECL 79 OR 80

ExplanationThe user specified an input data set that does not havethe required attributes (F or FB with LRECL 79 or 80).

Note: If the input data set has an LRECL of 79, SPUFIassumes the data set was exported by QMF. Therefore,it is recommended that you should not use an LRECLof 79 for a data set that is not exported from QMF.

User responseCorrect the input data set attributes, and try again.

DSNE378A ASA CONTROL CHARACTER NOTALLOWED ON INPUT DATA SETRECFM

ExplanationThe user attempted to use an input data set containingforms control characters or machine controlcharacters. These characters are not allowed on theinput data set.

User responseRemove the forms control characters or machinecontrol characters from the input data set, and tryagain.

DSNE379A text from DYNALLOC


ExplanationAn attempt to allocate a data set has failed. Thismessage contains the secondary explanation for thefailure.

User responseCorrect the condition, and resubmit the subcommand.

DSNE381A UNEXPECTED ALLOCATIONRETURN CODE return-code,reason-code

ExplanationAn unexpected return code from the z/OS DYNALLOC(SVC 99) service was received.

return-codeThe DYNALLOC return code.

reason-codeThe reason code that is associated with the returncode.

User responseSee the DYNALLOC reason and return codes todetermine how to correct the condition. Then resubmitthe subcommand.


DSNE383A INVALID OUTPUT DATA SETRECORD FORMAT. OPEN RETURNCODE rcode

ExplanationThe data set format was invalid. Acceptable recordformats are: F, FB, FBA, V, VB, or VBA.

User responseEnter a valid value in the record format field.

DSNE384A UNEXPECTED DEALLOCATIONRETURN CODE return-code,reason-code

ExplanationA deallocation request has returned an unexpectedreturn and reason code.

User responseRefer to the appropriate MVS publication forexplanations of the return and reason codes.

DSNE385A ENTER MEMBER NAME. INPUTDATA SET IS PARTITIONED

ExplanationThe input data set is partitioned, and the user did notenter the member name on the SPUFI main menu.

System actionProcessing does not begin until the panel entries arecorrect. If any of the processing options are changed,this message is ignored, and processing will proceedaccording to the new settings.

User responseEnter the member name.

DSNE386A MEMBER member-name NOTPRESENT IN SPECIFIED INPUTDATA SET

ExplanationThe named member is not in the input data set.

System actionProcessing does not begin until the panel entries arecorrect.

User responseEnter a correct member name or a correct data-set-name.

DSNE387I DSNTIAR ERROR. RETURN CODE =return-code

ExplanationAn internal Db2 error has occurred. DSNTIARattempted to format a message to explain a nonzeroSQL code, but the attempt failed.

System programmer responsePrint the ISPF log, and collect a dump of the TSOaddress space.






Related tasksDisplaying SQLCA fields by calling DSNTIAR(Db2 Application programming and SQL)Related referencePossible return codes from DSNTIAR (Db2Application programming and SQL)

DSNE388A INPUT DATA SET MUST BESEQUENTIAL OR PARTITIONED

ExplanationThe input data set organization is not recognized.


User responseEnter a data-set-name with sequential or partitionedorganization. It may be necessary to allocate asequential or partitioned data set.

DSNE389A A MEMBER HAS BEEN SPECIFIEDFOR A SEQUENTIAL DATA SET

ExplanationThe user has specified a member as input to SPUFI.However, the input data set specified is sequential.


User responseEnter the data-set-name without attempting to specifya member.

DSNE390A THE OUTPUT DATA SETATTRIBUTES ARE INCONSISTENT

ExplanationThis message indicates that the user made one ofthree possible errors in specifying block size andlogical record length (LRECL):

• The user specified a record format (RECFM) of F, butthe block size is not equal to the logical recordlength (LRECL)

• The user specified a record format (RECFM) of F, FB,or FBA, but block size is not evenly divisible bylogical record length (LRECL).

• The user specified a record format (RECFM) of VB,but the block size is less than logical record length(LRECL) + 4. The user must allow 4 bytes for theblock header.

User responseSpecify logical record length (LRECL) and block sizeappropriately on the DSNESP02 panel.

DSNE391I FREEMAIN ERROR IN MODULEmodule-name

ExplanationSPUFI encountered a FREEMAIN error in the specifiedmodule.

System actionThis message is logged in the ISPF log data set. Noabend occurs.

System programmer responsePrint the ISPF log, and collect a dump of the TSOaddress space. If you suspect an error in Db2, youmight need to report the problem. For informationabout identifying and reporting the problem, seeCollecting diagnostic data (Collecting data).

User responseNotify the system programmer or systemadministrator.

DSNE392I GETMAIN ERROR IN MODULEmodule-name

ExplanationSPUFI encountered a GETMAIN error in the specifiedmodule.

System actionThis message is logged in the ISPF log data set. Userabend X'00C50003' is issued.

System programmer responseEnsure that enough storage is allocated to the TSOuser.

User responseNotify the system programmer or systemadministrator.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_displaysqlcadsntiar.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_displaysqlcadsntiar.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_returncodedsntiar.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_returncodedsntiar.html


DSNE393I SPF VDELETE ERROR IN MODULEDSNESM90. ERROR CODE = flag

ExplanationAn internal SPUFI error has occurred. CSECTDSNESM90 tried to delete an ISPF dialog variable thatwas not previously defined.

System actionThis message is logged in the ISPF log data set. Noabend is issued. However, if the problem persists,notify the system programmer.


Problem determinationRecord the error code 'flag'. It has no user significance,but it can assist IBM Support in resolving the problem.

DSNE395I UNEXPECTED RETURN CODEFROM SPF SERVICE

ExplanationA return code of 4 from ISPF DISPLAY or a return codeof 8 from the ISPF editor was encountered.

System actionThe message is displayed on the SPUFI panel andlogged in the ISPF log data set. No user abend isissued.

System programmer responseIf a new release of ISPF is used, determine whetherthe above return codes are now assigned meaning byISPF.


Problem determinationThis message may be issued if a previously unassigned(by ISPF) return code from the ISPF DISPLAY or EDITfunction is encountered. If a new release of ISPF isused, determine whether the above return codes arenow assigned meaning by ISPF.

DSNE396A YOU CANNOT SPECIFY DEFERWHEN LEAVING SPUFI

ExplanationYou have attempted to leave SPUFI with outstandingdatabase changes not yet committed or rolled back.You can’t leave SPUFI unless a decision has beenmade to commit or rollback.


User responseSpecify COMMIT or ROLLBACK.

DSNE601I SQL STATEMENTS ASSUMED TO BEBETWEEN COLUMNS nn AND nn

ExplanationThis message indicates which record columns in theinput data set are scanned for SQL statements. Fordata sets of type COBOL, columns 8 through 72 arescanned. For STANDARD data set types, if the LRECL is79 then columns 1 through 71 are scanned, and if theLRECL is 80 then columns 1 through 72 are scanned.

System actionThis message is written to the SPUFI output data setalong with other summary messages.

DSNE603E INPUT STATEMENT HASUNBALANCED APOSTROPHES

ExplanationAn opening apostrophe was detected in an inputrecord, but the end of data set was reached before aclosing apostrophe was encountered.

System actionSPUFI processing stops. Correct the error, and startagain.

User responseA closing apostrophe was probably omitted from aliteral value. Add the missing apostrophe, and executethe input file again.

DSNE604E THE SQL STATEMENT EXCEEDSTHE MAXIMUM ALLOWED LENGTH




ExplanationThis message indicates that the preceding SQLstatement in the output data set exceeds themaximum length allowed. An SQL statement may spanup to a maximum of 29127 input records.


User responseEdit the SQL statement in question so that it resides onfewer input records.

DSNE605E THE INPUT DATA SET IS EMPTY

ExplanationThe user has specified an input data set that does notcontain any valid SQL statements.


User responseEdit SQL statements into the specified data set, orspecify another input data set that contains valid SQLstatements.

DSNE606E INVALID USE OF AN SQLSTATEMENT TERMINATOR

ExplanationAn SQL statement terminator has been usedimproperly in an SQL input statement. Either twosuccessive statement terminators were encountered,or a series of blanks followed by a terminator wasdetected. The proper use of the SQL statementterminator is to delimit the end of a valid SQLstatement.


User responseRemove the extraneous terminator from the input dataset.

DSNE607E PREVIOUS INPUT RECORD HASUNBALANCED SO/SICHARACTERS

ExplanationA shift out (SO) character was detected in the previousinput record with no corresponding shift in (SI)character in the record. The SO/SI characters delimit aDBCS string in the SPUFI input data set. SPUFIrequires that SO/SI characters be paired within aninput record.

System actionSPUFI processing stops.

User responseA closing SI character was probably omitted from aliteral value. Add the missing SI character, and re-execute the input file.

DSNE609E INPUT STATEMENT HASUNBALANCED QUOTES

ExplanationAn opening quote (“) was detected in an input record,but a corresponding quote was not found at the end.Two sets of quotes are used to delimit a statement.

System actionSPUFI processing stops.

User responseA closing quote was probably omitted from a literalvalue. Add the missing quote, and execute the inputfile again.

DSNE610I NUMBER OF ROWS DISPLAYED ISnn

ExplanationExecution of an SQL SELECT statement causes one ormore rows of data to be displayed. This messageappears in the output data set following the returneddata for a SELECT. It gives a count, 'nn', of the numberof rows displayed.

System actionInput data set processing is completed, and thismessage is included in the SPUFI output.


DSNE611I COLUMN HEADER name FORCOLUMN NUMBER nn WASTRUNCATED

ExplanationAn SQL SELECT statement was executed, but thespecified column name, identified by 'nn' in themessage, was truncated. This truncation occurredeither because the column name was longer than theremaining record width or because the name waslonger than the user-specified maximum field length.


User responseIf the truncation is caused by insufficient record width,use a larger LRECL for the output data set or specifyfewer data columns to be returned on the SELECTstatement.

If the truncation is caused by the user-specifiedmaximum field length setting, use a larger value forthis setting.

DSNE612I DATA FOR COLUMN HEADER nameCOLUMN NUMBER nn WASTRUNCATED

ExplanationAn SQL SELECT statement was executed, but data forthe specified column name, identified by 'nn' in themessage, was truncated. This truncation occurredeither because the data was longer than the remainingrecord width or because the data was longer than theuser-specified maximum field length.


User responseIf the truncation is because of insufficient recordwidth, use a larger LRECL for the output data set orspecify fewer data columns be returned on the SELECTstatement.

If the truncation is because of the user-specifiedmaximum field length setting, use a larger value forthis setting.

DSNE613I OUTPUT LRECL IS TOO SMALL TODISPLAY THE FOLLOWINGCOLUMNS:

ExplanationAn SQL SELECT statement was executed, but thelogical record length of the output data set was notlarge enough to display the column names and datavalues of all returned columns. The columns specifiedfollowing this message were not displayed because ofinsufficient remaining record width.


User responseThis condition can be avoided by using a larger LRECLfor the output data set or by specifying that fewer datacolumns be returned on the SELECT statement.

DSNE614I AUTOCOMMIT IS NO, NOCHANGES COMMITTED

ExplanationThe user delayed committing or rolling back changesmade during execution of the input file until later in thesession. This is done by specifying an AUTOCOMMIToption of 'NO'.


User responseCommit or roll back these changes before ending thesession.

DSNE615I NUMBER OF ROWS AFFECTED ISnn

ExplanationThis message is written to the output data setfollowing execution of an SQL data change statement,or REFRESH statement. nn is a count of the number ofrows that qualified to be deleted, inserted, or updatedby that statement, excluding rows affected by eithertriggers or referential integrity constraints. If theprevious SQL statement is a multiple-row FETCH, nnindicates the number of rows fetched. If an integerarithmetic overflow occurs during the calculation ofthe number of affected rows, nn is -1.


Note: In the case of a mass delete of a table in asegmented table space, or a delete from a view whenneither the DELETE statement nor the definition of theview included selection criteria, this message will notbe displayed. In these cases, Db2 does not access norcount the individual rows.


DSNE616I STATEMENT EXECUTION WASSUCCESSFUL, SQLCODE IS sql-code

ExplanationThis message is written to the output data setfollowing the successful execution of an SQLstatement from the input data set. The sql-code valuespecifies the SQL return code for the statement.


Related conceptsSQL codes (Db2 Codes)

DSNE617I COMMIT PERFORMED, SQLCODEIS sql-code

ExplanationWhen an input file is executed successfully and theuser specified an AUTOCOMMIT option of 'YES', thismessage is written to the output data set to indicatethe status of the COMMIT that was performed. The sql-code value specifies the SQL return code for theCOMMIT.



DSNE618I ROLLBACK PERFORMED, SQLCODEIS sql-code

ExplanationWhen an error is encountered while executing a SPUFIinput file, and the user specified an AUTOCOMMIToption of 'YES', this message will be written to the

output data set to indicate the status of the ROLLBACKthat was performed. sql-code specifies the SQL returncode for the statement.



DSNE620I NUMBER OF SQL STATEMENTSPROCESSED IS nn

ExplanationThis message is written to the output data set afterprocessing all SQL statements in the current input dataset. The term 'nn' is a count of the number of SQLstatements processed.


DSNE621I NUMBER OF INPUT RECORDSREAD IS nn

ExplanationThis message is written to the output data set afterprocessing all SQL statements in the current input dataset. The term 'nn' is a count of the total number ofrecords read from the input data set.


DSNE622I NUMBER OF OUTPUT RECORDSWRITTEN IS nn

ExplanationThis message is written to the output data set afterprocessing all SQL statements in the current input dataset. The term 'nn' is a count of the total number ofrecords written to the output data set.


DSNE623I SYNTAX ERROR AT RECORD xx,OFFSET xx


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_sqlcodes.html



ExplanationA syntax error was detected in the SQL statementpreceding this message in the output data set. 'xx'identifies the erroneous line number in the SQLstatement, and 'yy' identifies the offset (in characters)of the error within that record.


User responseCorrect the specified syntax error in the input data set,and execute the job again.

DSNE624I UNABLE TO LOAD ISPLINKMODULE. SPUFI PROCESSINGTERMINATED

ExplanationDuring SPUFI initialization processing, an error wasencountered attempting to LOAD the ISPF interfacemodule, ISPLINK. This module could not be located inthe LNKLST or STEPLIB library concatenation.

System actionSPUFI processing is terminated.

User responseRearrange your library concatenation so that theISPLINK module can be located. This module residesin the ISPF load library.

DSNE625I CONNECT TO LOCATION (location-name) PERFORMED, SQLCODE ISsql-code

ExplanationThe SPUFI user has indicated that the SQL statementsdefined in the input file are to be processed by theserver at the remote location specified in theCONNECT LOCATION field of the SPUFI panel.

This message appears in the output file and indicatesthat an SQL CONNECT request was issued by SPUFI tothe specified location name. The sql-code valuespecifies the SQL return code associated with theCONNECT request.

System actionSubsequent processing of the SQL statements in theinput file is based upon the successful completion ofthe CONNECT request. If the request is unsuccessful,the SQL error number and all associated errormessages are placed in the output file.

User responseRespond as indicated by the SQL code returned.


DSNE626I MAXIMUM OUTPUT LINES FORSELECT STATEMENT REACHED(number), PROCESSING FORCURRENT SELECT STATEMENTTERMINATED

ExplanationThe maximum number of output lines to be displayedfor a SELECT statement was reached. Processing ofthe current SELECT statement is terminated. Themaximum number to display is specified by the SPUFIuser on the CURRENT SPUFI DEFAULTS panel.

This message appears in the SPUFI output file.

System actionProcessing of subsequent SQL statements in the inputfile continues.

User responseIf the number of lines displayed is insufficient, you canincrease the maximum number of lines to be displayedfor SELECT statements on the CURRENT SPUFIDEFAULTS panel and re-execute the SELECTstatement.

DSNE627I csect-id FOR SQLCODE = sql-code,USER REQUESTED: action

ExplanationDuring PREPARE processing of the SQL statement,SPUFI received an SQLCODE (+495) and requestedyou to respond with the action to be taken by SPUFI(CONTINUE or BYPASS).

SPUFI does not consider this to be an SQL statementerror and places this message in the SPUFI output fileto document the SQLCODE received and the action yourequested. sql-code specifies the SQL return codeassociated with the PREPARE request.



System actionSPUFI processing for this statement is based on actiondocumented in the message:

• CONTINUE

– Processing for the current SQL statementcontinues normally.

• BYPASS

– Processing for the current SQL statement isterminated without error.

User responseRespond as indicated by the SQL code returned.

Related conceptsSQL codes (Db2 Codes)Related information+495 (Db2 Codes)

DSNE800A NO DEFAULT VALUES WERECHANGED. PRESS ENTER TOCONTINUE

ExplanationThe user left panel DSNESP02 without changing it.This panel contains all the defaults that can bemodified by the user.

System actionThis message is presented on the SPUFI panelDSNESP01. SPUFI waits for the next user input.

User responsePress 'ENTER' if you want to continue.

DSNE803A INPUT FILE WAS NOT CHANGED.PRESS ENTER TO CONTINUE

ExplanationThe user has exited from the ISPF editor withoutmodifying the input data set.

System actionThe system waits for the next user input.

User responsePress 'ENTER' if you want to continue. The SPUFIpanel variable settings can be changed at this point.

DSNE804A TO CONTINUE, C (COMMIT) OR R(ROLLBACK) MUST BE SPECIFIED

ExplanationThe user has specified the AUTOCOMMIT=NO optionand now wants either to exit or to switch to anotherDb2 subsystem with outstanding work uncommittedon the current Db2 subsystem.

System actionDb2 waits for the user to specify either the COMMIT(C) or the ROLLBACK (R) option.

User responseEnter 'C' or 'R' to continue.

DSNE808A EDIT SESSION HAS COMPLETED.PRESS ENTER TO CONTINUE.

ExplanationThe user has exited from the ISPF editor.

System actionSPUFI waits form the next user input.

User responsePress 'Enter' if you want to continue. Press 'END' if youwant to terminate your SPUFI session. The SPUFIpanel variable settings can be changed at this point.

DSNE901I EXECUTION COMPLETE

ExplanationExecution of a subcommand has successfullycompleted.


DSNE903I WARNING, DECLARATION HASSAME NAME AS TABLE table-name

ExplanationA DCLGEN subcommand has a 'STRUCTURE'parameter that is the same as the 'table name'specified in the message. The requested declarationhas been created, but this could cause conflicts withinternal names.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/p495.html

System actionDCLGEN execution continues.

User responseChoose a different 'STRUCTURE' parameter.

DSNE904I EXECUTION COMPLETE, MEMBERmember-name REPLACED

ExplanationA DCLGEN subcommand executed successfully,replacing the 'member-name' specified in themessage.


DSNE905I EXECUTION COMPLETE, MEMBERmember-name ADDED

ExplanationA DCLGEN subcommand executed successfully, addingthe 'member-name' specified in the message to thedata set specified in the DCLGEN subcommand.


DSNE908E csect-name INVALID USE OFparameter IN PARAMETER LIST OFKEYWORD keyword.

ExplanationAn invalid parameter was specified in the parameterlist of the specified keyword.

System actionSubcommand processing is terminated. The TSOattachment facility is ready for more input.

User responseCorrect the parameter list in error, and resubmit thejob.

Severity8

DSNE909E csectname WARNING,DBCSSYMBOL KEYWORD IS

INVALID WITH LANGUAGElanguage KEYWORD IGNORED

ExplanationYou specified the DBCSSYMBOL keyword in yourDCLGEN invocation, but your LANGUAGE keywordvalue was not COB2. DBCSSYMBOL only applies toCOB2 PICTURE clauses. DCLGEN will ignore thiskeyword.

System actionDCLGEN processing continues.

User responseIn the future, do not specify the DBCSSYMBOLkeyword unless the LANGUAGE keyword value isCOB2.

DSNE910E csectname WARNING, THEOWNER KEYWORD WASSPECIFIED WITH A QUALIFIEDTABLE NAME. OWNER KEYWORDIGNORED

ExplanationYou specified both the OWNER keyword and aqualified table name for the TABLE keyword in yourDCLGEN invocation. The table qualifier will be used asthe table owner, and the OWNER keyword will beignored.


User responseIn the future, specify either a qualified table name forthe TABLE keyword, or an unqualified table name forthe TABLE keyword along with the OWNER keyword.

DSNE920E member-name ALREADY EXISTS,SPECIFY ACTION(REPLACE) TOREPLACE

ExplanationThe DCLGEN user tried to overwrite an old declarationwith a new one without specifying REPLACE on the'ACTION' parameter.



User responseChange the 'ACTION' parameter to REPLACE (if that’sactually what you want to do), and resubmit thecommand.

DSNE921E REQUIRED PARAMETER table-parameter IS MISSING

ExplanationYour DCLGEN subcommand was missing the requiredTABLE parameter.

System actionYour DCLGEN subcommand was not processed. TheDSN command processor issued a return code of 8.DSN is ready for more input.

User responseResubmit the DCLGEN subcommand with a TABLEparameter.

DSNE922E TABLE NAME QUALIFIER OFqualifier IS TOO LONG. CANNOTEXCEED 8 CHARACTERS INLENGTH

ExplanationDCLGEN detected an invalid TABLE parameter. Thetable name qualifier (the left portion of the tablename) was too long.

System actionYour DCLGEN subcommand was not processed. TheDSN command processor issued a return code of 8.DSN is ready for more input.

User responseResubmit the DCLGEN subcommand with a shortertable name qualifier.

DSNE923E CSECT csect-name FOUND ANUNRECOGNIZED LANGUAGEunknown

ExplanationThis is a DCLGEN subsystem error, not a user error. Thelanguage parameter unknown is not known to thesubsystem.


System programmer responseRe-create the problem with DSN tracing turned on.Collect the trace stream in the DSNTRACE data set.Use the ABEND subcommand of the DSN commandprocessor to collect a dump. If you suspect an error inDb2, you might need to report the problem. Forinformation about identifying and reporting theproblem, see Collecting diagnostic data (Collectingdata).

User responseReport the problem to the system programmer.

DSNE924E PARSE FAILED IN CSECT csect-name PARAMETER parm, FLAGflag

ExplanationThis is a Db2 subsystem error, not a user error. The'PARM' parameter was not correctly parsed. The flagspecified was detected as an inappropriate value in aparse results field.


System programmer responseRe-create the problem with DSN tracing turned on.Collect the trace stream in the DSNTRACE data set.Use the ABEND subcommand of the DSN commandprocessor to collect a dump. If you suspect an error inDb2, you might need to report the problem. Forinformation about identifying and reporting theproblem, see Collecting diagnostic data (Collectingdata).

User responseReport the problem to the system programmer.

DSNE925E BUFFER OVERFLOW IN CSECTcsect-name WHILE WRITINGstring

ExplanationThis is a DCLGEN subsystem error. CSECT 'csect-name'detected a buffer overflow condition while attemptingto write 'string'.







System programmer responseRe-create the problem with DSN tracing turned on.Collect the trace stream in the DSNTRACE data set. Ifyou suspect an error in Db2, you might need to reportthe problem. For information about identifying andreporting the problem, see Collecting diagnostic data(Collecting data).


DSNE926E COMMAND REJECTED - commandNOT SUPPORTED UNDERcommand_processor

ExplanationThe user entered a TSO TIME or TEST command.These are not supported by DSN or DB2I.

System actionThe user should leave DSN or DB2I, return to TSO, andretry the command. DSN can be run under TSO TEST.The TSO attachment facility is ready for more input.

User responseEnter the DSN subcommand, or leave DSN to executethe requested command.

DSNE927E RUN SUBCOMMANDS REQUIRE(1)PROGRAM PARM OR (2)PLANAND CP PARMS

ExplanationRUN subcommands may contain (1) the 'PROGRAM'parameter and, optionally, the 'PLAN' parameter or (2)the 'PLAN' and command processor ('CP') parameters.Combinations of (1) and (2) are not allowed.


User responseCorrect the subcommand, and resubmit the job.

DSNE928E RUN SUBCOMMANDS CANNOTHAVE A PROGRAM PARM AND ACP PARM

ExplanationA RUN subcommand cannot contain both the'PROGRAM' and command processor ('CP')parameters. The subcommand should be resubmittedwith only one of the parameters.


User responseCorrect the subcommand, and resubmit the job.

DSNE929E TABLE NAME LOCATION OF(location-name) IS TOO LONG.CANNOT EXCEED 16 CHARACTERSIN LENGTH.

ExplanationDCLGEN detected an invalid AT(location) keywordparameter. The specified location name is too long.

System actionYour DCLGEN subcommand was not processed. TheDSN command processor issues a return code of 8.The DSN is ready for more input.

User responseResubmit the DCLGEN subcommand specifying alocation name that does not exceed 16 characters.

DSNE930E TABLE NAME OF table-name MUSTBE QUALIFIED WHEN SPECIFIEDWITH LOCATION OF location-name

ExplanationDCLGEN detected an invalid TABLE keywordparameter. You must specify a qualified table namewith the AT (location) keyword.

System actionYour DCLGEN subcommand was not processed. TheDSN command processor issues a return code of 8.DSN is ready for more input.

User responseSpecify a qualified table name and resubmit theDCLGEN command.




DSNE931E csect-name keyword-name(parameter_value) CONTAINS ANINVALID SYMBOL (symbol)

ExplanationAn invalid 'symbol' (symbol) was specified in the'parameter_value' associated with the specified'keyword-name'.


User responseCorrect the keyword 'parameter_value' in error, andresubmit the job.

Severity8

DSNE932I WARNING, ONLY IBM SUPPLIEDnames SHOULD BEGIN WITH DSN

ExplanationThe user has issued a BIND, REBIND, or FREEsubcommand, using a name or id that begins withDSN.


User responseIn the future, do not use plan-names, collection-ids,package -ids, or service-names that begin with DSN. Itwould be a good idea to FREE the plan, package, orservice you just created and to BIND again with a newplan-name, collection-id, package-id, or service-name.

DSNE935I ... IS THE DCLGEN COMMANDTHAT MADE THE FOLLOWINGSTATEMENTS

ExplanationThis message is a part of normal DCLGEN output. Itidentifies the DCLGEN command that produced thedeclaration of which it is a part.

System actionThis message is included in the DCLGEN output.

DSNE936I THE NUMBER OF COLUMNSDESCRIBED BY THISDECLARATION IS nnn

ExplanationThis message is a part of normal DCLGEN output. Ittells how many columns were in the table that wasnamed in the DCLGEN command.


DSNE937I COBOL DECLARATION FOR TABLEtable-name

ExplanationThis message is a part of normal DCLGEN output. Ittells the name of the table for which the declarationwas created.


DSNE938I PLI DECLARATION FOR TABLEtable-name



DSNE939E csect-name THE COMBINATIONACQUIRE(ALLOCATE) ANDRELEASE(COMMIT) IS NOTALLOWED

ExplanationThe BIND or REBIND subcommand was submittedwith conflicting parameters.You cannot specifyACQUIRE(ALLOCATE) and RELEASE(COMMIT) on thesame subcommand.

System actionThe subcommand is terminated and the DSNcommand processor reissues theDSN prompt to allowanother subcommand to be entered.


User responseEnter the corrected subcommand.

Related tasksChoosing a RELEASE option (Db2 Performance)Related referenceBIND PACKAGE (DSN) (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)REBIND PLAN (DSN) (Db2 Commands)ACQUIRE bind option (Db2 Commands)RELEASE bind option (Db2 Commands)

DSNE940E DEFER(PREPARE) INVALID WITHNODEFER(PREPARE)

ExplanationThe BIND or REBIND subcommand was submittedwith conflicting parameters. You cannot specifyDEFER(PREPARE) and NODEFER(PREPARE) on thesame subcommand because these actions conflict.

System actionThe subcommand is terminated and the DSNcommand processor reissues the DSN prompt to allowanother subcommand to be entered.


Related referenceBIND PACKAGE (DSN) (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)REBIND PLAN (DSN) (Db2 Commands)DEFER and NODEFER bind options (Db2Commands)

DSNE941I DSNBIND IS A RESERVED PLANNAME

ExplanationThis message is generated when the plan name is'DSNBIND' in a BIND statement.


User responseChange the plan-name and resubmit the job.

DSNE942E csect-name REMOTE CONNECTIONNAME (parameter-value) HASINVALID FORMAT

ExplanationThe REMOTE connection name (parameter-value)contains a < or> character in the starting or endingposition of the parameter, but the parameter value isnot bracketed by both characters. This message is alsogenerated if the first character of the connection nameis not an alphabetic character.

If the LU name format of the REMOTE keyword is to beused, the name must be specified as <LU-name>.

System actionSubcommand processing is terminated. DSNcommand processor reissues the DSN prompt to allowanother subcommand to be entered.

User responseCorrect the keyword (parameter-value) in error, andresubmit the job.

Severity8

Related referenceDSNH (TSO CLIST) (Db2 Commands)

DSNE943E csect-name REMOTE CONNECTIONNAME (parameter_value) CANNOTEXCEED (length_value)CHARACTERS IN LENGTH

ExplanationThe REMOTE connection name (parameter_value)specified is greater than the length (length_value)permitted for the REMOTE keyword.

This message is issued if the REMOTE location nameformat exceeds 16 characters, or the LU name format(<LU name>) exceeds 10 characters in length.

System actionSubcommand processing is terminated. DSNcommand processor reissues the DSN prompt to allowanother subcommand to be entered.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_choosereleaseoption.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_bindpackage.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_bindplan.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_rebindpackage.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_rebindplan.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptacquire.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptrelease.html





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptdeferandnodefer.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptdeferandnodefer.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_dsnh.html

User responseCorrect the keyword (parameter_value) in error andresubmit the job.

Severity8


DSNE944I WARNING, BECAUSE YOUR TABLEOR COLUMN NAMES CONTAINLOWER CASE OR NON-ALPHABETIC CHARACTERS, YOUWILL NEED TO USE THE SQL (NOTPL/I) INCLUDE STATEMENT TOINCLUDE DCLGEN OUTPUT INTOYOUR PROGRAM

ExplanationDCLGEN had to wrap your table or column name(s) inquotes so Db2 could process them. Quotes are notrecognized by the PL/I compiler. To avoid compilationerrors, use the SQL INCLUDE statement ('EXEC SQLINCLUDE member-name') to merge the DCLGEN outputwith your source program.


User responseIf you have not coded the SQL INCLUDE, do so beforethe next compile.

Related referenceDCLGEN (DECLARATIONS GENERATOR) (DSN)(Db2 Commands)INCLUDE (Db2 SQL)

DSNE947I QUOTE PARAMETER IS ONLYVALID WITH COBOL. IT HAS BEENCHANGED TO APOST

ExplanationYou specified the DCLGEN QUOTE parameter and anon-COBOL language parameter. This combination isnot valid. The QUOTE parameter was specified aseither a parameter on the DCLGEN subcommand or adefault set for your site at Db2 installation time.

The DCLGEN processor changed the QUOTE setting(for this run) to APOST.

System actionDCLGEN processing continues and should producevalid output.

User responseIf you used QUOTE on the DCLGEN command, you maywant to change it to APOST before submitting it again.

DSNE948I csect-id FURTHER subcommandPROCESSING WILL NOT BEATTEMPTED

ExplanationA DSN command processor subcommand (indicated inthe message) has encountered an error which stoppedDSN from processing this subcommand. Thesubcommand will not complete normally. Thismessage is accompanied by other messagesexplaining the exact nature of the problem.

System actionSubcommand processing terminates. The DSN promptis reissued, indicating DSN is ready for anothersubcommand.

User responseRead the accompanying messages for help in decidingwhat to do next.

DSNE949E COMMIT PROCESSING ABNORMALTERMINATION, REASON CODEreason_code

ExplanationThe DSN command processor has initiated a 'prepareto commit' request in Db2. The request is rejectedwhen Db2 cannot commit the work performed

System actionCommit processing is terminated.

User responseExamine the reason code associated with thismessage, and respond as indicated beforeresubmitting the job.

Problem determinationReference the associated reason code to determinewhy the 'prepare to commit' was not successful.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_dclgen.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_dclgen.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_include.html

DSNE950E DCLGEN DOES NOT SUPPORT THElang LANGUAGE

ExplanationA DCLGEN user attempted to specify a LANGUAGEparameter, 'lang', that DCLGEN does not support.

System actionDCLGEN processing terminates.

User responseCorrect the LANGUAGE parameter and resubmit theDCLGEN subcommand.

DSNE952I C DECLARATION FOR TABLE table-name



DSNE953I csect-name PRECISION OFDECIMAL COLUMN colnameEXCEEDS THE MAXIMUMPRECISION FOR THE langLANGUAGE.

ExplanationDCLGEN was building a COBOL or PL/I languagedeclaration for a table when it encountered a decimalcolumn with a precision greater than the precisionsupported by the language.

System actionDCLGEN set the return code to 4 and processed therest of the table.

User responseThis is a warning. Be aware that the declaration forcolumn 'colname' causes a compiler error. You mustedit the declaration before including it in anapplication program.

DSNE954I csect-name USE OF THE DCLGENCOLSUFFIX(YES) OPTION WILLRESULT IN A MIXED FIELD NAMEFOR COLUMN colname. THE lang

LANGUAGE DOES NOT SUPPORTMIXED FIELD NAMES.

ExplanationThe COLSUFFIX(YES) option and a double-byteNAMES prefix were specified in a DCLGEN invocation,but column colname contains single-byte characters.This combination would result in a generated fieldname with a mixture of double-byte and single-bytecharacters, but the lang language does not supportmixed field names.

System actionDCLGEN set the return code to 4 and generated thefield name as requested.

User responseThis is a warning. Be aware that the declaration forcolumn colname causes a compiler error. You mustedit the declaration before including it in anapplication program.

DSNE955I csect-name COLSUFFIX(YES) WASSPECIFIED WITHOUT A NAMESPREFIX. COLUMN NAMES WILL BEUSED FOR FIELD NAMES

ExplanationWhen COLSUFFIX(YES) is specified in a DCLGENinvocation, DCLGEN generates field names byconcatenating the NAMES prefix with the columnnames. However, no NAMES prefix was specified.

System actionDCLGEN set the return code to 4 and used the columnnames as field names.

User responseThis is a warning. Specify a NAMES prefix when youspecify COLSUFFIX(YES).

DSNE956A A FIELD NAME PREFIX MUST BESPECIFIED WHEN COLUMNSUFFIX VALUE IS YES.

ExplanationWhen YES is specified for the COLUMN SUFFIX field onthe DCLGEN panel, DCLGEN generates field names byconcatenating the value in the FIELD NAME PREFIXfield with the column names. However, no value wasspecified for FIELD NAME PREFIX.


System actionThe DCLGEN panel generated this error message.

User responseSpecify a FIELD NAME PREFIX value, or change theCOLUMN SUFFIX value to NO.

DSNE957I THE LENGTH OF ONE OR MORENAMES EXCEEDS THE STANDARDMAXIMUM ALLOWED BY THElanguage LANGUAGE

ExplanationDCLGEN was building a COBOL or PL/I languagedeclaration for a table when it generated a hostvariable name that is longer than the languagepermits.

languageThe language that the declaration uses: COBOL orPL/I

The new declaration might cause a compiler error.

System actionDCLGEN issues return code to 4 and processes the restof the table.

User responseIf you want to use this declaration in an application,edit the declaration so that the length of the hostname variable is within the permitted range for thelanguage.

DSNE958I DCLGEN DOES NOT SUPPORT THESQL DATA TYPE data-type(SQLTYPE sql-type) FOR THElanguage LANGUAGE

ExplanationThe specified table or view contains a column with adata type that is either not supported by or notrecognized by DCLGEN.

data-typeThe data type of the column.

sql-typeNumeric representation of the data type.

languageThe programming language that was used for thedata declaration: COBOL, PL/I, C, or C++.

System actionDCLGEN issues return code 8 and finishes processingthe table. A declaration for the table or view is created,but it is incomplete and will not compile successfullywithout modifications.

User responseIf the reported data type is UNKNOWN, contact IBMSupport and provide the SQLTYPE value andprogramming language from the message.

For all other data types, verify that the data type thatyou want to use is supported by DCLGEN. If the datatype that you originally chose is not supported, youmight be able to identify an alternate data type. If youwant to use the table or view declaration that DCLGENcreated, update the generated declaration by eitherremoving the column or changing the data type.

DSNE960E PARAMETER STRING EXCEEDSALLOWABLE LIMIT OF 100(DECIMAL) CHARACTERS

ExplanationThe PARMS option parameter-string of the RUNsubcommand cannot exceed 100 (decimal) charactersin length.


User responseCorrect the PARMS option and resubmit the job.

DSNE964E csect-name INVALID SYNTAX FORkeyword KEYWORD PARAMETERparameter

ExplanationA parameter that does not follow Db2 namingconventions was specified for keyword.

System actionSubcommand processing is terminated. The DSNcommand processor reissues the DSN prompt to allowyou to enter another subcommand.

User responseCorrect the keyword parameter value in error, andresubmit the command.


Related referenceBIND and REBIND options for packages, plans,and services (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)BIND PACKAGE (DSN) (Db2 Commands)REBIND PLAN (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)

DSNE965E parameter-value IS NOT A VALIDkeyword KEYWORD PARAMETER

ExplanationThe parameter-value is not a valid parameter value forthe keyword.

System actionSubcommand processing terminates. The DSNcommand processor reissues the DSN prompt to allowyou to enter another subcommand.

User responseCorrect and reissue the subcommand.

Related referenceBIND and REBIND options for packages, plans,and services (Db2 Commands)DYNAMICRULES bind option (Db2 Commands)BIND PACKAGE (DSN) (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)REBIND PLAN (DSN) (Db2 Commands)

DSNE966E connection-type KEYWORDOMITTED FROM THE ENABLE|DISABLE DECLARATION

ExplanationThe connection-type keyword was not specified ineither the ENABLE or DISABLE keywords and isrequired if connection-names are specified for theconnection-type.

System actionSubcommand processing is terminated. DSNcommand processor reissues the DSN prompt to allowyou to enter another subcommand.

User responseCorrect the connection type parameter with valuesthat are supported on the ENABLE and DISABLEkeywords and reissue the subcommand.

Related referenceENABLE and DISABLE bind options (Db2Commands)

DSNE967E keyword-name KEYWORD CANNOTBE SPECIFIED MORE THAN ONCEPER RUN

ExplanationEither the BIND PACKAGE MEMBER or LIBRARYkeywords specified more than one parameter value.Only one member or library name is permitted.

System actionSubcommand processing is terminated. The DSNcommand processor reissues the DSN prompt to allowanother subcommand to be entered.


Severity8

Related referenceBIND PACKAGE (DSN) (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)MEMBER bind option (Db2 Commands)LIBRARY bind option (Db2 Commands)

DSNE969E csect-name keyword1 ISMUTUALLY EXCLUSIVE WITHkeyword2

ExplanationBoth the PKLIST and NOPKLIST keywords, cannot bespecified on one invocation of the REBIND PLANsubcommand. Both the ENABLE and DISABLEkeywords cannot be specified on one invocation of theBIND/REBIND PLAN/PACKAGE subcommand.

System actionSubcommand processing is terminated. DSNcommand processor will reissue the DSN prompt toallow another subcommand to be entered.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindrebindoptions.html








https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptdynamicrules.html





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptenableanddisable.html




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptmember.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptlibrary.html

Severity8

Related referencePKLIST and NOPKLIST bind options (Db2Commands)ENABLE and DISABLE bind options (Db2Commands)BIND PLAN (DSN) (Db2 Commands)BIND PACKAGE (DSN) (Db2 Commands)REBIND PLAN (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)

DSNE970E EITHER MEMBER OR PKLIST MUSTBE SPECIFIED, BOTH ARE ALSOALLOWED

ExplanationThe BIND PLAN subcommand requires either theMEMBER or PKLIST keyword, and neither wasspecified. Either keyword or both may be specified.

System actionSubcommand processing is terminated. DSNcommand processor will reissue the DSN prompt toallow another subcommand to be entered.


Severity8

Related referenceBIND PLAN (DSN) (Db2 Commands)MEMBER bind option (Db2 Commands)PKLIST and NOPKLIST bind options (Db2Commands)

DSNE971E EITHER MEMBER OR COPY BUTNOT BOTH MUST BE SPECIFIED

ExplanationThe BIND PACKAGE subcommand requires either theMEMBER or COPY keyword; both are not allowed onthe same subcommand invocation.

System actionSubcommand processing is terminated and the DSNcommand processor will reissue the DSN prompt toallow another subcommand to be entered.

User responseEnter the corrected subcommand

Severity8

Related referenceBIND PACKAGE (DSN) (Db2 Commands)

DSNE974E csect-name keyword1 KEYWORDIS INVALID WITH keyword2KEYWORD.

ExplanationThe keyword2 cannot be specified with keyword1.

System actionSubcommand processing is terminated. The DSNcommand processor reissues the DSN prompt to allowanother subcommand to be entered.

User responseModify one of the keywords on the command andresubmit the job.

Related referenceBIND PACKAGE (DSN) (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)

DSNE975E csect-name keyword KEYWORD ISONLY VALID WHEN COPYKEYWORD IS PRESENT

ExplanationA keyword was issued that may only be specified inconjunction with the COPY keyword.keyword

COPYVER or OPTIONS

System actionSubcommand processing is terminated. The DSNcommand processor will reissue the DSN prompt toallow another subcommand to be entered.


Severity8


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptpklistandnopklist.html









https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptmember.html







DSNE976E LIBRARY KEYWORD IS ONLYVALID WHEN MEMBER KEYWORDIS PRESENT

ExplanationThe LIBRARY keyword may only be specified inconjunction with the MEMBER keyword.

System actionSubcommand processing is terminated. The DSNcommand processor will reissue the DSN prompt toallow another subcommand to be entered.


Severity8





Chapter 4. DSNF messagesMessage identifiers that begin with DSNF communicate information about the message generator.

DSNF001I MESSAGE GENERATORINITIALIZATION PARAMETERSNOT FOUND. DEFAULTS ASSUMED

ExplanationThe message generator was unable to access therouting code initialization parameter defined by theDSN6SYSP macro. Default values defined by thatmacro are assumed.

System actionSubsystem initialization continues.


System programmer responseIt might be necessary to change the DSN6SYSP macroand replace the DSN6SYSP member of the DSNIPARMdirectory.

Related tasksDefining Db2 initialization parameters:DSNTIJUZ (Db2 Installation and Migration)

DSNF700I csect-name message-id HAS BEENISSUED

ExplanationAn unsuccessful attempt has been made to issue themessage 'message-id'. This message is issued only ifthe requested message could not be found in the Db2message directory.

System actionThe system proceeds as though the requestedmessage had been issued.


System programmer responseRefer to this manual for actual message text. You needthe message number ('message-id'). If you suspect anerror in Db2, you might need to report the problem.For information about identifying and reporting theproblem, see Collecting diagnostic data (Collectingdata).


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntijuzaddmember.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntijuzaddmember.html




Chapter 5. DSNG messagesMessage identifiers that begin with DSNG communicate information about the database descriptormanager.

DSNG001I EDM stype CAN NOT BEDECREASED BELOW THE VALUEisize SPECIFIED AT DB2 STARTUP

ExplanationThe EDM stype storage cannot be decreased below thesize that was specified at Db2 startup.


DSNG002I EDM storage-type HAS AN INITIALSIZE initial-size, REQUESTED SIZErequested-size, AND ANALLOCATED SIZE allocated-size

ExplanationThe size of an EDM storage pool has been changed.

storage-typeThe type of EDM storage pool that was updated.Possible values are:

Value Description

DBD CACHE EDM DBD pool

RDS ABOVE EDM RDS pool above

RDS BELOW EDM RDS pool below

SKELETON EDM statement pool

STMT POOL EDM skeleton pool

initial-sizeThe storage size prior to the request for a change.

requested-sizeThe requested storage size.

allocated-sizeThe storage size in effect immediately after therequest for a change.

If the request was for an increase to the EDM pool size,the allocated-size value is the storage available tosatisfy the request.

If the request was for a decrease to the EDM pool size,the allocated-size value is the initial-size valuereduced by the amount that could be releasedimmediately. When the allocated-size value is larger

than the requested-size value, the difference is markedto be released when it is no longer referenced.



Related conceptsEDM storage (Db2 Performance)

DSNG003I INSUFFICIENT VIRTUAL STORAGETO EXPAND EDM stype STORAGE

ExplanationInsufficient virtual storage exists to expand the EDMstype storage as specified.

System actionThe EDM stype storage is expanded only to the sizeallowed by the available virtual storage.

DSNG004I EDM stype HAS A FINALALLOCATED SIZE asize

ExplanationThis message is issued in response to a request todecrease the EDM stype storage. The message isissued when the requested new level is reached.stype

The EDM pool that is being reduced. Possiblevalues are Pool, DBD Pool, or Statement Pool.

asizeThe EDM stype storage that is available.


DSNG005I DBD IS INCONSISTENT WITH THECATALOG. UNABLE TO FIND AROW IN SYSTABLES WITH DBIDdbid AND OBID obid.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_edmstorage.html

ExplanationThis message is issued in response to a request to loada database with DBID dbid. This message is issuedwhen the row is not found in SYSTABLES.dbid

DBID of the database that is being loaded.obid

OBID of a table in the database.

System actionDBD could not be loaded.

Operator responseBased on dbid and obid from the message, verify thatthe row does not exist in the Catalog. REPAIR DBDTEST or DIAGNOSE can be run to gather morediagnostic information. Once you have determined thatthe Catalog contains the correct information, REPAIRDBD REBUILD can be run to rebuild the DBD.

Severity8 (error).

DSNG006I DBD IS INCONSISTENT WITH THECATALOG. UNABLE TO FIND AROW IN SYSCOLUMNS WITH DBIDdbid, OBID obid, AND COLUMNNUMBER colno.

ExplanationThis message is issued in response to a request to loada database with DBID dbid. This message is issuedwhen the row is not found in SYSCOLUMNS.dbid

DBID of the database that is being loaded.obid

OBID of a table in the database.colno

Column number in the table.

System actionDBD could not be loaded.

Operator responseBased on dbid/obid/colno from the message, verifythat the row does not exist in the Catalog. REPAIR DBDTEST or DIAGNOSE can be run to gather morediagnostic information. Once you have determined thatthe Catalog contains the correct information, REPAIRDBD REBUILD can be run to rebuild the DBD.

Severity8 (error).

DSNG007I DB2 CATALOG LEVEL (catalog-level) CODE LEVEL (code-level)MODE (system-mode)

ExplanationThis message is issued when the database descriptorfor the Db2 catalog is loaded into memory. It displaysthe Db2 catalog and code release levels and a modeindicator.

catalog-levelFour-character indicator of the Db2 catalog releaselevel.1010

Db2 101110

Db2 11code-level

Four-character indicator of the Db2 code releaselevel.1010

Db2 101110

Db2 11system-mode

Two- or three-character indicator of the currentmode of the system:Cn

Conversion modeCn*

Conversion mode, but the system detects thatit has been to a higher level

EnEnabling-new-function mode

En*Enabling-new-function mode, but the systemdetects that it has been to a higher level

NNew-function mode




Related conceptsDb2 migration modes (Db2 Installation andMigration)

DSNG008I EDM RDS BELOW STORAGE HASAN INITIAL LIMIT initial-limit ANDA NEW LIMIT new-limit.

ExplanationThe limit for EDM RDS BELOW storage has beenchanged. The new limit takes effect immediately.

initial-limitThe limit prior to the request for a change.

new-limitThe limit in effect after the request for a change.

A resource unavailable condition can occur whenthe limit is decreased and the amount of storage in usewas already at or near the new limit.



Related tasksDesigning EDM storage space for performance(Db2 Performance)

DSNG009I csect-name TABLE SPACEDSNDB01.SPT01 IS IN REORGPENDING STATE

ExplanationThe change to the inline length of the SPTSEC_DATAcolumn of SPT01 is complete, and the new length isshorter than the current length.


System action:The SPT01 table space is placed in restrictive REORG-pending (REORP) state.

User response:Reorganize the SPT01 table spaces to remove theREORP state. When the SPT01 table space is in REORPstate binds cannot be processed.

Related referenceSPT01 INLINE LENGTH field(SPT01_INLINE_LENGTH subsystemparameter) (Db2 Installation and Migration)

DSNG010I csect-name SPT01 INLINE LENGTHCHANGE SUCCESSFUL, LENGTHnew-size

ExplanationThe SPT01 inline length was successfully changed.


new-sizeThe new inline length, in bytes.




DSNG011I csect-name SPT01 INLINE LENGTHCHANGE UNSUCCESSFUL,LENGTH size

ExplanationThe SPT01 inline length was not changed.


sizeThe size of the inline length in bytes.


User response:Check the console for a DSNT500I message.


Chapter 5. DSNG messages 163

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_db2migrationmodes.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_db2migrationmodes.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_designedmstoragespace.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_designedmstoragespace.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_spt01inlinelength.html










Chapter 6. DSNH messagesMessage numbers that begin with DSNH communicate information about the Db2 precompiler or the Db2coprocessor.

References to the Db2 precompiler will also apply to the Db2 coprocessor, unless otherwise mentioned.The Db2 coprocessor is invoked through the compiler.

Message line numbersThe line number nnnn in DSNH messages is generated by assigning sequential numbers to the originalsource. The numbers are printed on the SQL Db2 precompiler source listing (if the SOURCE option isspecified to the precompiler). If you are using the Db2 coprocessor, the error messages and their linenumbers, if applied, are printed on the compiler output listing. The line number points to the beginning ofthe SQL statement. The column number, if it can be determined, is a relative number from the beginningof the SQL statement that is in error.

'COL cc' in the messages identifies the source column in which the condition was detected. The indicatedcolumn, 'cc', usually specifies the location of the column containing the first character of the associatedsource token. However, if the precompiler cannot determine this location, it is the beginning of thestatement. Because the detected error might be similar to a valid, but different, construction, the SQLparsing might indicate the wrong location for the error.

Message severity codesOne of the characters I, W, E, S, or U is shown at the beginning of each precompiler message as an aid tothe programmer. These characters indicate the severity level as follows:

I 0 Informational

W 4 Warning

E 8 Error

S 12 Severe error

U 16 Unrecoverable error

When unsupported non-Db2 statements are detected during SQL(ALL) precompilation, the return codewill be forced to 4 if the return code was 8, and no host-related errors were detected. This is done so thatthe application can proceed with the compilation and link-edit steps. This allows the syntax checking tobe delayed until bind. If a severity 8 precompiler error message is not a host-related error, theprecompiler treats the error as a warning and place a W instead of an E in the precompiler output listing.In this instance, the precompiler also issues DSNH049I to indicate that the actual return code 8 from theprecompiler was changed to 4.

The following precompiler messages with severity levels of 8 are not changed from errors to warningswhen SQL(ALL) is in effect:

• DSNH051I• DSNH080I• DSNH290I• DSNH291I• DSNH292I• DSNH312I• DSNH313I• DSNH314I


• DSNH504I

Source tokensTokens from your source program do not always appear in messages exactly as they appear in yourprogram. For example, leading zeros are removed from integer tokens.

DSNH003I S csectname FILE ddnamePARAMETERS INCORRECT

ExplanationThe file ddname has invalid or incorrect parameters,such as logical record length.

System actionThe precompiler is terminated.

User responseCorrect the data set or library parameters.


DSNH004I S csectname type COULD NOT BEFOUND

ExplanationThe precompiler could not find the indicated type ofstatement in the application program source. Thismessage is only issued for HOST(COBOL) andHOST(COB2). The type is DATA DIVISION, WORKING-STORAGE SECTION, or PROCEDURE DIVISION. Thiserror can cause other errors.

System actionProcessing continues. Additional errors might result.

User responseEnsure that the host language statement in yourapplication program is correct and that the statementis present within the proper margins.


DSNH005I U csectname FILE ddname NOMEMBER NAME SPECIFIED

ExplanationThe ddname must refer to a partitioned data set, andthe member name must be specified in the allocation.This helps to prevent accidental erasure of the DBRMlibrary.


User responseCorrect the JCL or TSO allocate command to specify amember name.

Severity16 (unrecoverable error)

DSNH006I U csectname FILE ddname COULDNOT BE OPENED

ExplanationThe file identified in the message is required, but itcould not be opened.


System programmer responseEnsure that the SYSIN data is provided. Also ensurethat SYSLIB is defined if the application programcontains SQL INCLUDE statements.

User responseEnsure that the file is present in your JCL.


DSNH007I E csectname LINE nnnn COL ccILLEGAL CHARACTER IGNORED:'c' ('hh'X)


ExplanationThe character identified in the message as c is notpermitted. The hexadecimal representation for thecharacter is hh.

System actionThe character is ignored.

User responseCorrect the character. You might need to place thecharacter within quotation marks or apostrophes.Check to ensure that the CCSID in which the source iswritten matches the CCSID option for the Precompiler.For example, if the CCSID 1047 codepoints for left andright square brackets (hexadecimal 'AD' and 'BD') areused in a C source program, ensure that thePrecompiler CCSID option is CCSID(1047).

Severity8 (error)

DSNH008I S csectname LINE nnnn COL ccNESTED INCLUDE NOTSUPPORTED

ExplanationWhile processing an INCLUDE, another nestedINCLUDE statement was encountered.

System actionThe nested INCLUDE statement is ignored.

User responseRemove the nested INCLUDE statements; they are notallowed in an included file. The Db2 precompilerpermits only one level of INCLUDE statements.


DSNH009I S csectname LINE nnnn COL ccMEMBER name COULD NOT BEINCLUDED

ExplanationThe identified member name was not found or couldnot be read.

System actionProcessing continues without the data from thatmember.

User responseEnsure that the member is in the library and that itsname is spelled correctly. Check and correct any JCLerrors. They are likely to cause other errors. Ensurethat the data set and library parameters are correct.


DSNH010I S csectname LINE nnnn COL ccUNTERMINATED STRINGCONSTANT BEGINNING text

ExplanationThe constant identified in the message as 'text' is notterminated properly.

System actionThe string is treated as if it were terminated by the endof file.

User responseTerminate the string constant. Check for and correctany missing or extra quotation marks and apostrophes.These errors are likely to cause others. Somestatements were probably missed because of missingor extra string delimiters.


DSNH011I S csectname LINE nnnn COL ccUNTERMINATED COMMENT

ExplanationA comment is not terminated properly. This message isonly issued for HOST(PLI) and HOST(C).

System actionThe string is treated as if it were terminated by the endof file.

User responseEnsure that the comment terminator is typed properlyand that it is within the specified margins. This error is

Chapter 6. DSNH messages 167

likely to cause others. Some statements were probablymissed because of the missing comment terminator.


DSNH012I W csectname LINE nnnn COL ccINVALID CONTINUATION

ExplanationThe continuation does not follow the host languagerules.


User responseFollow the host language continuation rules andembedded SQL continuation rules. Check the marginoption. This error is most common in assemblerlanguage in cases where a continuation begins beforethe continuation column (the continuation column iscolumn 16 by default).

Severity4 (warning)

DSNH013I E csectname LINE nnnn COL cc SQLSTATEMENT FOUND OTHER THANIN THE FIRST PROGRAM (ORMAIN PROGRAM)

ExplanationThis message is for VS COBOL II only. If any SQLstatement is found in the source after the first programin a BATCH COMPILE or the end of the main programof a nested program, this message is issued.


User responseMove up the SQL statement and corresponding hostvariable declaration to the main program or to the firstprogram and resubmit the job.

Severity8 (error)

DSNH014I S csectname LINE nnnn COL cc SQLSTATEMENT IS FOUND IN ANINAPPROPRIATE PLACE

ExplanationIf any SQL statement is found in the COBOLDECLARATIVES section, this message is issued.


User responseMove the SQL statement out of the COBOLDECLARATIVES section and resubmit the job.


DSNH016I E csectname LINE nnnn COL cctoken REQUIRED

ExplanationThe required character or keyword identified as tokenis missing.

System actionThe token is assumed to be present in order tocontinue checking the statement syntax.

User responseCorrect the SQL statement. Determine if you skippedeither this keyword or another keyword earlier in theSQL statement. The assumed token is printed in theSYSTEM error message. This token might not be whatyou intended, even though it is the only symbolallowed in the clause at this point.

Severity8 (error)

DSNH019I W csectname OPTION: INVALIDOPTION option

ExplanationThe identified option was requested, but it is not aprecompiler option.

System actionThe option is ignored.


User responseCheck the valid precompiler options to determine ifyour spelling is correct for this option. This problemmight cause additional errors if the APOST, APOSTSQL,COMMA, HOST, MARGINS, QUOTESQL, or TWOPASSoption is needed but not specified. The other optionsare either defaults or affect only the listing. Correct theproblem and run the precompile again.

Severity4 (warning)

DSNH021I W csectname OPTION:SUBOPTION NOT PERMITTEDWITH OPTION option

ExplanationThe identified option cannot have suboptions, but oneor more were specified.

System actionThe suboptions are ignored.

User responseNone is required. However, you should remove thesuboption.

Severity4 (warning)

DSNH022I W csectname OPTION:UNMATCHED ')' TAKEN AS ','

ExplanationAn unmatched ending parenthesis was found beforethe end of the option string.

System actionThe parenthesis is assumed to be a comma.

User responseBalance the parentheses.

Severity4 (warning)

DSNH023I W csectname OPTION:SUBOPTION MISSING FOROPTION option

ExplanationThe specified option requires a suboption, but one wasnot provided.


User responseProvide a suboption or remove the option. Thisproblem might cause additional errors if the HOST orMARGINS option is needed but not specified. Theother options are either defaults or affect only thelisting. Correct the problem and run the precompileagain.

Severity4 (warning)

DSNH024I W csectname OPTION:SUBOPTION suboption INVALIDFOR OPTION option

ExplanationThe identified suboption is not allowed for the optionspecified.

System actionThe entire option is usually ignored.

User responseRefer to the 'options used' list in the precompileroutput listing to see if the option was used. Removethe suboption.

Severity4 (warning)

DSNH025I W csectname OPTION: EXCESSIVESUBOPTIONS FOR OPTION option

ExplanationToo many suboptions were given for the identifiedoption.

System actionThe excess suboptions are ignored.


User responseRemove excess suboptions.

Severity4 (warning)

DSNH026I W csectname OPTION: INVALIDMARGINS FOR HOST LANGUAGE

ExplanationThe host language does not permit the specifiedmargins.

System actionThe MARGINS option is ignored.

User responseEnsure that the source statements are within theproper margins and that the margins are specifiedcorrectly. The margins for COBOL must be 8, 72. Themargins for FORTRAN must be 1, 72.

Severity4 (warning)

DSNH027I W csectname SUBOPTIONsuboption TOO LONG, TRUNCATEDAFTER numofchar CHARS

ExplanationThe version ID is greater than numofchar bytes long.The maximum length for the version ID is 64 bytes.

System actionThe option is honored, but the version ID is truncatedafter 64 bytes.

User responseRefer to the 'options used' list in the precompileroutput to see what version ID was used.

Severity4 (warning)

DSNH028I W csectname ATTACH SUBOPTIONsuboption NOT PERMITTED WITHHOST (FORTRAN) SPECIFIED.

ExplanationThe identified suboption for precompiler optionATTACH cannot take effect when the application is aFORTRAN application because the interface code forFORTRAN is always DSNHFT.


User responseNone is required. However, you can either codeATTACH(TSO) or specify no ATTACH precompileroption

Severity4 (warning)

DSNH029I E csectname LINE nnnn COL ccINTO CLAUSE REQUIRED

ExplanationSELECT statements embedded in an applicationprogram must have an INTO clause to denote wherethe results of the SELECT are to be placed. DynamicSELECT statements do not permit the INTO clause.

System actionThe statement is replaced by host languagestatements that, if executed, set an error code in theSQLCA.

User responseAdd the INTO clause to the SELECT statement, andprecompile the application program again.

Severity8 (error)

DSNH030I W csectname LINE nnnn COL ccSTATEMENT CONTAINS WRONGNUMBER OF 'INTO' VARIABLES

ExplanationThe number of variables specified in an INTO clause isnot the same as the number of select-list elements(taking into account expansion of host structures and'*' or 'table.*' select entries according to thedeclarations supplied).



User responseEnsure the included table declarations are correct. Ifthe declarations are correct, this statement causes anerror when the application program is bound. If thedeclarations are incorrect, you can proceed, but thedeclarations should be corrected. Otherwise, you needto correct the SQL statement and precompile again.

Severity4 (warning)

DSNH031I W csectname LINE nnnn COL ccSTATEMENT CREATES A COLUMNWITH NAME name1 WHICH DOESNOT MATCH DECLARED NAMEname2

ExplanationThe column name specified in a CREATE statement(name1) is not the same as the name of thecorresponding column in the DECLARE TABLEstatement (name2).


User responseEnsure that the DECLARE TABLE matches the CREATETABLE. You can use the cross-reference and sourcelistings to help find the two statements.

Severity4 (warning)

DSNH032I W csectname LINE nnnn COL ccSTATEMENT CREATES A COLUMNname WHOSE ATTRIBUTES DONOT MATCH THE DECLARATION

ExplanationThe column name is specified in a CREATE statementwith a different data type or length than was specifiedfor the corresponding column in the DECLARE TABLEstatement.


User responseCorrect the DECLARE TABLE or CREATE TABLEstatement. If the DECLARE TABLE statement isincorrect, some warnings might also be incorrect ormight not be generated when needed. If the CREATETABLE statement is incorrect, you must correct it.

Severity4 (warning)

DSNH033I W csectname LINE nnnn COL ccSTATEMENT CREATES MORE ORLESS COLUMNS THAN WEREDECLARED

ExplanationThe number of columns specified in a CREATEstatement is different from the number of columnsspecified in the DECLARE TABLE statement.


User responseEnsure that the DECLARE TABLE matches the CREATETABLE. If the DECLARE TABLE statement is incorrect,some warnings might also be incorrect or might not begenerated when needed. If the CREATE TABLEstatement is incorrect, you must correct it.

Severity4 (warning)

DSNH034I W csectname LINE nnnn COL ccSTATEMENT INSERTS MORE ORLESS VALUES THAN THE NUMBEROF COLUMNS DECLARED

ExplanationThe number of values specified in an INSERToperation is different from the number of columnsspecified in the DECLARE TABLE statement for thereceiving table.


User responseInsert the correct number of values. If the DECLARETABLE statement is incorrect, this warning might also


be incorrect. If the INSERT operation is incorrect, youmust correct it.

Severity4 (warning)

DSNH038I S csectname LINE nnnn COL ccPROGRAM OR SUBPROGRAMCONTAINS MORE THAN 32767SQL STATEMENTS

ExplanationThe number of SQL statements in an applicationprogram or a FORTRAN subprogram is greater than32767.

System actionThe precompiler terminates.

User responseDivide the application program or subprogram intosmaller programs or reduce the SQL statements ineach program unit so that the maximum number ofSQL statements is not exceeded.


DSNH041I W csectname OPTION: MISSINGHOST OPTION

ExplanationThe host language was not specified in the OPTIONfield.

System actionHOST(COBOL) is assumed.

User responseSpecify the host language if it is not COBOL. It isprobably best to specify the host language and removeall warnings.

Severity4 (warning)

DSNH042I W csectname OPTION: optionOPTION INVALID FOR HOSTLANGUAGE

ExplanationThe option identified in the message is not valid. TheQUOTE and COMMA options are not permitted withHOST(ASM), HOST(PLI), or HOST(C). The TWOPASSoption is not permitted with HOST(COBOL).

System actionThe specified option is ignored.

User responseRemove the invalid option, or correct the hostspecification.

Severity4 (warning)

DSNH049I W csectname RETURN CODE ISFORCED TO 4 BECAUSE OPTIONSQL(ALL) IS IN EFFECT, ORIGINALRETURN CODE WAS nnn

ExplanationOne or more SQL-related error messages weredetected by the precompiler, but because of optionSQL(ALL), the return code is forced to 4 in order to letthe application proceed with compilation.

The SQL syntax checking is deferred until bind timebecause the source might contain non-Db2 SQL syntaxthat the Db2 precompiler does not recognize and flagsas an error. The DBRM produced by thisprecompilation cannot be bound successfully by Db2 ifthere are SQL syntax errors or non-Db2 SQL syntax.

The return code remains untouched if there are host-related syntax or semantic errors in the source.


User responseEnsure that the intention of this precompilation is forexecuting it in a non-Db2 system.

Severity4 (warning)

DSNH050I I csectname WARNINGS HAVEBEEN SUPPRESSED DUE TO LACKOF TABLE DECLARATIONS


ExplanationOne or more warning messages were suppressedbecause no table declarations were found before thefirst SQL statement that referenced a table or column.

System actionProcessing continues. Suppression is discontinued if atable declaration is found.

User responseInsert (or INCLUDE) table declarations before they arereferenced in order to permit table and columnchecking.

Severity0

DSNH051I E csectname LINE nnnn COL ccsqltype name PREVIOUSLYDECLARED OR REFERENCED

ExplanationThe variable sqltype is TABLE, CURSOR, orSTATEMENT. The identifier name was already definedwith the given sqltype. The definition might haveoccurred implicitly. For example, name might havebeen found in the FROM clause of a SELECT, causing itto be defined as a table.

System actionThe name is installed in the symbol table as aduplicate.

User responseRemove duplicate definitions, or correct thereferences. Avoid implicit definitions by inserting (orincluding) table declarations before they arereferenced. Check the number of passes used. Use thecross-reference and source listings to help resolve thistype of error.

Severity8 (error)

DSNH052I E csectname LINE nnnn COL ccCOLUMN name IS ALREADYDEFINED IN TABLE table-name

ExplanationThe identified name is already defined as a column inthe table named table-name. The definition might haveoccurred implicitly. For example, table-name mighthave been found in a select-list, causing name to bedefined as a column within table-name if table-namewas not declared as a host variable.

System actionThe name is installed in the symbol table as aduplicate.

User responseRemove duplicate definitions, or correct thereferences. Avoid implicit definitions by inserting (orincluding) table declarations before they arereferenced.

Severity8 (error)

DSNH053I W csectname NO SQLSTATEMENTS WERE FOUND

ExplanationNo SQL statements were found in the precompilerinput file. An empty DBRM member was written.


User responseIf you embedded SQL statements in your applicationprogram and none were found, make sure your columnmargins are properly defined for your applicationprogram.

Severity4 (warning)

DSNH057I E csect-name LINE line-numberCOL column number RETURNSTATEMENT IN AN SQL FUNCTIONMUST RETURN A VALUE

ExplanationA RETURN statement is specified without a value in anSQL function. The return value must be specified.



line-number and column numberThe location of the error in the source program.

System actionThe statement can not be processed.

User responseAdd a return value to the statement, and try therequest again.

Severity8 (error)

DSNH060I E csectname LINE nnnn COL ccINVALID type SPECIFICATION:spec

ExplanationThe type is either SCALE or LENGTH. The spec is thegiven SCALE or LENGTH specification in an SQLdeclaration. Length and scale specifications must beunsigned integers. The scale specification, wherepermitted, cannot exceed the length. The lengthspecification cannot be 0.


User responseCorrect the length or scaling.

Severity8 (error)

DSNH078I E csect-name LINE line-numberCOL column number PARAMETERNAMES MUST BE SPECIFIED FORROUTINE routine-name

ExplanationThe routine does not have parameter names specifiedfor all parameters.



routine-nameThe name of the routine.

When the SQL routine is defined with LANGUAGE SQL,a parameter name is required for each parameter thatis defined. For native SQL procedures, LANGUAGE SQLis optional, but for external SQL procedures,LANGUAGE SQL is required.

System actionThe statement cannot be processed.

Programmer responseEnsure that each defined parameter includes aparameter name.

Severity8 (error)

DSNH080I E csectname LINE nnnn COL ccusage VARIABLE name IS NOT typeTYPE

ExplanationThe usage is INDICATOR or STRING. The type isSMALLINT, VARCHAR, or CHARACTER. The data typeof the variable name is not acceptable. All indicatorvariables must be small integers. PREPARE andEXECUTE strings must be variable character strings,except for FORTRAN, which requires character type.

System actionIf the containing SQL statement is a declaration, it isdiscarded. If the containing SQL statement isexecutable, it is replaced by host language statementsthat will, if executed, set an error code in the SQLCA.

User responseSpecify a host variable of the proper type.

Severity8 (error)

DSNH081I W csectname LINE nnnn COL ccSTATEMENT DOES NOT CONFORMTO ANS SYNTAX STANDARD -REASON CODE ccc


ExplanationWhen the precompiler option STDSQL(YES) is in effect,the SQL syntax is checked to see if it conforms to theANSI/ISO SQL standard of 1992. Reason codes are:000

Aggregate function with DISTINCT as anarithmetic-operation operand does not conform tothe ANSI/ISO SQL standard of 1992.

001FOR UPDATE OF as part of a DECLARE CURSORstatement does not conform to the ANSI/ISO SQLstandard of 1992.


System programmer responseCheck the SQL statement.

User responseYou have the option of changing or not changing thesyntax to conform to the ANS syntax standard.

Severity4 (warning)

DSNH083I I csectname LINE nnnn COL cc IBMSQL RESERVED WORD ibmkeywdSPECIFIED AS AN IDENTIFIERNAME

ExplanationWhen the precompiler option SQL(ALL) is in effect,IBM SQL reserved words should not be used asidentifier names. Using IBM SQL reserved words limitsthe portability of the statement.


User responseIf possible, change the identifier name to a non-IBMSQL reserved word so that the statement conforms tothe IBM SQL standard. Not changing the identifiername means that the program is less portable withinthe IBM SQL environment.


DSNH084I W csectname LINE nnnn COL ccUNACCEPTABLE SQL STATEMENT

ExplanationThe referenced SQL statement is not allowed in thissituation, but it will not cause an error. Depending onthe option specified at precompile time, one of thefollowing occurred.

• The BEGIN DECLARE SECTION(*), END DECLARESECTION(*), and UPDATE STATISTICS statementsare flagged as not compatible.

* For C applications, BEGIN and END DECLARESECTION are not flagged.

* For other languages, the statement is only allowedwith precompiler option STDSQL(YES).

• Using the STDSQL(YES) precompiler option, theINCLUDE SQLCA statement is flagged as a warning.

System actionThe BEGIN DECLARE SECTION, END DECLARESECTION, and INCLUDE SQLCA statements areignored. The other statements are replaced by hostlanguage statements that will, if executed, set awarning code or SQLCODE -84 in the SQLCA.

User responseUnless this application program is used in a portablemanner, remove the statement.

Severity4 (warning)

DSNH088I W csectname LINE nnnn COL ccTHIS STATEMENT WILL action ANENTIRE TABLE

ExplanationThe action is either DELETE or UPDATE. Thereferenced SQL statement has no WHERE clause andwill delete or update all rows of the specified table.This message is printed as a warning to theprogrammer.


User responseBe sure that you intend to delete or update all rows, oradd a suitable WHERE clause.


Severity4 (warning)

DSNH090I S csectname LINE nnnn COL ccHOST VARIABLE NOT PERMITTEDHERE: name

ExplanationHost variable references are not permitted in this typeof SQL statement. The name is invalid.

System actionThe statement is replaced by host languagestatements that will, if executed, set an error code inthe SQLCA.

User responseSpecify a literal or a column name rather than a hostvariable. The colon (:) indicates that the name thatfollows is a host variable. Remove it to specify acolumn name.


DSNH091I I csectname LINE nnnn COL ccEBCDIC CCSID used for string-expression.

ExplanationIn a PL/1 application program, a string-expression wasspecified for a PREPARE or EXECUTE IMMEDIATEstatement, and the precompiler-generated structuresfor this string-expression specify an EBCDIC CCSID.


User responseIf you intended that the string-expression should betreated as a string expression, then no action isrequired.

If the string-expression consists of just one hostvariable, and you intended that the string-expressionshould be treated as a host variable, then the hostvariable must be preceded by a colon, and at least oneDECLARE VARIABLE statement must be contained inyour program source.

If you add a DECLARE VARIABLE for any host variablein your program source, and re-precompile your

application, the variable previously treated as a string-expression by the precompiler will be treated as a hostvariable and this message will not be issued.


DSNH097I E csectname LINE nnnn COL cc.THE USE OF LONG VARCHAR ORLONG VARGRAPHIC IS NOTALLOWED IN THIS CONTEXT.

ExplanationThe statement attempted to use the LONG VARCHARor LONG VARGRAPHIC syntax. This syntax cannot beused for the following statements:

• CAST syntax• CREATE DISTINCT TYPE• CREATE FUNCTION• CREATE PROCEDURE• ALTER FUNCTION• COMMENT ON FUNCTION• GRANT EXECUTE ON FUNCTION• REVOKE EXECUTE ON FUNCTION


User responseCorrect and reissue the failing statement.

Severity8 (error)

DSNH101I S csectname THE STATEMENT ISTOO LONG OR TOO COMPLEX.

ExplanationThe statement cannot be executed because it exceedsthe system limits for either length or complexity.


User responseBreak the statement into shorter or less complex SQLstatements.


Severity16

DSNH102I E csectname STRING CONSTANTIS TOO LONG. STRING BEGINSstring

ExplanationThe string constant beginning with string has a lengthgreater than the maximum allowed length. Moststrings have these limits:

• For a hexadecimal constant (X, GX, or UX), thenumber of hexadecimal digits must not exceed32704.

• Any other character string constant must be shortenough so that its UTF-8 representation requires nomore than 32704 bytes.

• Any other graphic string constant must be shortenough so that its UTF-8 representation requires nomore than 32704 bytes.

• The sum of the lengths of the UTF-8 representationsof the constant values in an ENDING AT clause mustnot exceed 765 bytes. This clause applies to CREATETABLE, ALTER TABLE, CREATE INDEX, or ALTERINDEX.

In some contexts, however, the limit is smaller.

For special registers, the allowable length depends onthe particular special register. A string that exceedsthe limit can be specified only through assignmentfrom a host variable. If this release of Db2 increasesthe maximum allowed length of a string constant, thenan attempt to exploit the new length before using theNew Function Mode produces this SQL return code.

Two consecutive string delimiters are used torepresent one string delimiter within the characterstring, but these count as 2 bytes when calculating thelengths of character string constants.

System actionIf the SQL statement containing the string is adeclaration, it is discarded. If the SQL statementcontaining the string is executable, it is replaced byhost language statements that, if executed, set anerror code in the SQLCA.

User responseCorrect the string. If a shorter string is acceptable,reduce the length of the string constant. If a long stringis required, a host variable is required.

Severity8 (error)

Related conceptsSQL communication area (SQLCA) (Db2 SQL)Related referenceLimits in Db2 for z/OS (Db2 SQL)

DSNH103I E csectname constant IS ANINVALID NUMERIC CONSTANT

ExplanationThe token was found. It begins with a digit, but it is nota valid integer, decimal, or float literal. Identifierscannot begin with a digit except for the WHENEVERstatement with HOST(FORTRAN), and the identifiers inCOBOL.


User responseCheck the indicated token for validity. For a characterliteral, use apostrophes or quotation marks. For anumber, remove the invalid characters.

Severity8 (error)

DSNH104I E csectname LINE nnnn COL ccILLEGAL SYMBOL "token". SOMESYMBOLS THAT MIGHT BE LEGALARE: token-list

ExplanationA syntax error was detected where the symbol "token"occurs in the SQL statement. The list of symbols thatmight be legal shows some alternate symbols thatcould possibly be correct at that point, if the precedingpart of the statement is entirely correct.

However, the preceding part of the statement might beincorrect. For example, if an important keyword isomitted, Db2 detects the error later, and not alwaysimmediately after the point where the keyword shouldappear. The list of alternate symbols are onlysuggestions.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sqlcommunicationsareaintro.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_limits.html


User responseCorrect the statement and precompile the programagain.

Severity8 (error)

DSNH105I E csectname LINE nnnn COL cc,INVALID STRING CONSTANTS

ExplanationIncorrect graphic or mixed data literals were found online nnnn, column cc.

System actionThe literal is ignored and the SQL statement containingthe problem is discarded.

System programmer responseCheck for a quote, an apostrophe, shift-out (so) orshift-in (si) characters, G or N characters, or thenumber of characters within the literal.

User responseSpecify the correct format of literals.

Severity8 (error)

DSNH107I E csectname LINE nnnn COL cc THENAME name IS TOO LONG.MAXIMUM ALLOWABLE SIZE ISsize

ExplanationThe identified name values exceeded the maximumsupported length.

If this release of Db2 increases the maximum allowedlength of a name, then an attempt to exploit the newlength when the value of the NEWFUN option is NO willproduce this message.

System actionIf the SQL statement containing the problem is adeclaration, it is discarded. If the SQL statementcontaining the problem is executable, it is replaced byhost language statements that will, if executed, set anerror code in the SQLCA.

User responseCorrect the name length.

Severity8 (error)

Related conceptsSQL communication area (SQLCA) (Db2 SQL)Related referenceLimits in Db2 for z/OS (Db2 SQL)

DSNH109I E csect-name LINE nnnn COL ccclause-type CLAUSE NOTPERMITTED

ExplanationA clause was used where it is not permitted.


nnnn and ccThe location of the clause, stated as a line numberand column number.

clause-typeThe type of clause.

Possible causes for this message can include:

• A SELECT INTO statement cannot include a FORUPDATE OF clause, because position is not retained.

• SELECT clauses used in cursor declarations orsubselects cannot have an INTO clause because theINTO clause is on the FETCH statement.

• A SELECT INTO statement cannot specify a KEEPUPDATE LOCKS clause, except in a USE AND KEEPUPDATE LOCKS clause.

• CREATE VIEW statements cannot include any of thefollowing clauses:

– INTO– ORDER BY– FOR UPDATE– USING– LARGE– CORRELATION NAME




• The UNION operator is not allowed in an embeddedSELECT clause.

• A CREATE TABLESPACE statement cannot specifyLOCKPART without the NUMPARTS option.

• An ALTER TABLESPACE statement cannot specifyLOCKPART for a non-partitioned table space.

• A table space with LOCKPART YES cannot be alteredto LOCKSIZE TABLESPACE.

• A table space with LOCKSIZE TABLESPACE cannotbe altered to LOCKPART YES.

• The LARGE clause without the NUMPARTS option isnot allowed in a CREATE TABLESPACE statement.

• DESCRIBE INPUT statement can not have USINGclause.

• The table being updated in a POSITIONED UPDATEstatement can not be assigned a correlation name.

• On a CREATE INDEX statement, the INCLUDE clauseis not allowed for any of the following indexes:

– A non-unique index– A partitioning index, when index-controlled

partitioning is being used– An XML index– An extended index


User responseRemove the clause. You might need to use a cursor toperform the processing. The ORDER and FOR UPDATEclauses are accepted on the DECLARE CURSORstatement. The INTO clause is accepted on the FETCHstatement. The LARGE clause is accepted on a CREATETABLESPACE statement with the NUMPARTS option.

Severity8 (error)

Related referenceStatements (Db2 SQL)

DSNH110I E csectname INVALIDHEXADECIMAL CONSTANTBEGINNING constant

ExplanationThe string constant that begins with the specifiedstring is invalid because it has at least one of thefollowing errors:

• the string constant contains one or more charactersthat are not valid hexadecimal digits

• the string constant does not have an even number ofdigits

• for a UX or GX string constant, the number of digits isnot a multiple of 4


User responseCorrect the string constant.

Severity8 (error)

DSNH111W W csectname LINE nnnn COL ccTHE SUBPAGES OPTION IS NOTSUPPORTED FOR TYPE 2 INDEXES

ExplanationYou cannot use the SUBPAGES option for type 2indexes.

System actionThe option is ignored; processing continues.

Programmer responseRemove the SUBPAGES option to get rid of thewarning.

Severity4 (warning)

DSNH113I E csectname LINE nnnn COL ccINVALID CHARACTER FOUND INstring, REASON CODE - nnn

ExplanationThe string contains an invalid character. It can be anSQL ordinary identifier name, a host variable name, ora DBCS comment.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_statementsintro.html

Certain SQL identifiers (for example names of bufferpools, databases, and plans) must contain onlyuppercase alphabetic or national characters andnumerics; the first character must be alphabetic ornational.

The following reason codes apply to SBCS identifiers:

000An invalid character was found in the SBCSidentifier (including the case in which a DBCSidentifier was used where only an SBCS identifier isallowed).

The following reason codes apply to DBCS identifiersor comments:

101An odd number of bytes exists between the shift-out and the shift-in character.

102Either a shift-in or shift-out character is missing.

103DBCS blanks X'4040' are not allowed.

104There are no characters between the shift-out andthe shift-in characters.

105Shift-out cannot be the first byte of the DBCScharacter between the shift-out and the shift-incharacters.

System actionProcessing is terminated.

User responseCorrect the name.

Severity8 (error)

DSNH115I E csectname LINE nnnn COL ccILLEGAL USE OF COMPARISONOPERATOR operator

ExplanationThe syntax is not correct for this type of comparison. Asimple comparison such as '>' must not be followed bya list of items. The ANY and ALL comparisons mustprecede a subselect, rather than an expression or a listof items.


User responseCorrect the syntax.

Severity8 (error)


DSNH117I E csectname LINE nnnn COL ccSTATEMENT INSERTS THE WRONGNUMBER OF VALUES

ExplanationThe number of entries in a value-list is not the same asthe number of columns specified in an INSERTstatement.



Severity8 (error)


DSNH120I E csectname LINE nnnn COL ccFUNCTION USAGE NOTPERMITTED: fname

ExplanationA WHERE clause or SET clause contains an aggregatefunction, possibly as a result of a reference to acolumn that is derived from an aggregate function in aview definition. An aggregate function is allowed in aWHERE clause only if that clause appears within asubquery of a HAVING clause.





User responseCorrect the syntax. A subselect clause might beneeded to produce the function result.

Severity8 (error)

Related conceptsQueries (Db2 SQL)Related referencesubselect (Db2 SQL)

DSNH125I E csectname LINE nnnn COL ccINVALID ORDER BY COLUMNNUMBER: number

ExplanationThe identified column number is either less than 1 orgreater than the number of items in the select-list.

System actionThe cursor declaration is discarded.

User responseCorrect the column number.

Severity8 (error)

Related conceptsQueries (Db2 SQL)

DSNH126I E csectname LINE nnnn COL ccORDER BY CANNOT BE USEDWITH A FOR UPDATE OF CLAUSE

ExplanationThe ORDER BY clause makes the cursor incapable ofbeing updated.

System actionThe cursor declaration is discarded.

User responseThis is a Db2 restriction. You can have either anordered cursor or a cursor that can be updated. Youcannot specify both attributes for the same cursor. Youmight need to change your application logic.

Severity8 (error)

DSNH129I E csectname LINE nnnn COL ccTOO MANY TABLES SPECIFIED INSQL STATEMENT

ExplanationIn a subselect, (including all subqueries), there can beno more than 225 references to table names.


User responseReduce the number of table references in eachsubselect. Each reference to a single table countsseparately. The count only applies to table/viewreferences in the FROM list. Each view is only countedone time.

Severity8 (error)

Related referencesubselect (Db2 SQL)from-clause (Db2 SQL)Limits in Db2 for z/OS (Db2 SQL)

DSNH130I E csectname LINE nnnn COL cc THEESCAPE CLAUSE 'x' CONSISTS OFMORE THAN ONE CHARACTER

ExplanationThe literal x used in the ESCAPE clause is too long.Only one SBCS or one DBCS character is allowed.

System actionThe corresponding SQL statement is replaced by hostlanguage statements that will, if executed, set an errorcode in the SQLCA.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_queriesintro.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_subselect.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_subselect.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_fromclause.html


User responseCorrect the string. The literal string for the ESCAPEclause can only be one SBCS or DBCS character.

Severity8 (error)

DSNH131I E csectname LINE nnnnSTATEMENT WITH LIKEPREDICATE HAS INCOMPATIBLEDATA TYPES

ExplanationIf the column name at the left of LIKE or NOT LIKE is acharacter type, the expression at the right must be acharacter type. If the column name is a graphic type,the expression at the right must be a graphic type.

System actionThe statement is ignored.

User responseCheck the data type of every operand.

Severity8 (error)

DSNH132I E csectname LINE nnnn COL ccINVALID LIKE PREDICATE

ExplanationThe value following LIKE must be an alphanumerichost variable or literal, graphic host variable or literal,or special character literal.


User responseCorrect the syntax of the LIKE predicate.

Severity8 (error)

Related conceptsLanguage elements (Db2 SQL)

Related referenceLIKE predicate (Db2 SQL)

DSNH142I E csectname LINE nnnn COL cc THESQL STATEMENT IS NOTSUPPORTED

ExplanationThe token was found. An SQL statement was detectedthat is not supported by the database. The statementmight be valid for other IBM relational databaseproducts or it might be valid in another context. Forexample, statements such as VALUES and SIGNALSQLSTATE can appear only inside a trigger.

System actionThe SQL statement is replaced by host languagestatements that will, if executed, set an error code inthe SQLCA.

User responseChange the syntax of the SQL statement or remove thestatement from the program.

Severity8 (error)

DSNH170I E csectname LINE nnnn COL ccNUMBER OF ARGUMENTSSPECIFIED FOR function-name ISINVALID

ExplanationAn SQL statement specified the scalar functionfunction-name with either too many or too fewarguments.

System actionIf the containing SQL statement is a declaration, it isdiscarded. If the containing SQL statement isexecutable, it is replaced by host language statementsthat, if executed, sets an error code in the SQLCA.

User responseCorrect the function call.

Severity8 (error)

Related referenceScalar functions (Db2 SQL)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_langelementsoverview.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_likepredicate.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_scalarfunctionsintro.html

DSNH171I E csect-name LINE nnnn COL ccTHE DATATYPE, LENGTH, ORVALUE OF ARGUMENT nn OFfunction-name IS INVALID

ExplanationThe data type, length, or value of the argument nn of afunction-name scalar function is incorrect.

System actionIf the containing SQL statement is a declaration, it isdiscarded. If the containing SQL statement isexecutable, it is replaced by host language statementsthat, if executed, sets an error code in the SQLCA.

User responseCorrect the argument.

Severity8 (error)

Related referenceScalar functions (Db2 SQL)

DSNH182I E csectname LINE nnnn COL cc ANARITHMETIC EXPRESSION WITHA DATETIME VALUE IS INVALID

ExplanationThe specified arithmetic expression contains animproperly used date/time value or labeled duration.


User responseCorrect the indicated expression.

Severity8 (error)

Related conceptsDate arithmetic (Db2 SQL)Time arithmetic (Db2 SQL)Timestamp arithmetic (Db2 SQL)

DSNH184I E csectname LINE nnnn COL cc ANARITHMETIC EXPRESSION WITHA DATETIME VALUE CONTAINS APARAMETER MARKER

ExplanationThe specified expression contains a parameter markerimproperly used with a date/time value.


User responseCorrect the indicated expression.

Severity8 (error)

Related conceptsDate arithmetic (Db2 SQL)Time arithmetic (Db2 SQL)Timestamp arithmetic (Db2 SQL)

DSNH198I E csectname LINE nnnn COL ccEMPTY SQL STATEMENT IGNORED

ExplanationThe referenced SQL statement has no text betweenthe EXEC SQL and the statement terminator.

System actionThe statement is ignored.

User responseCorrect the statement, or remove it.

Severity8 (error)

DSNH199I E csectname LINE nnnn COL ccINVALID KEYWORD keyword;VALID SYMBOLS ARE: token list

ExplanationA syntax error was detected at the keyword specifiedin the message. As an aid to the programmer, a partial



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_datearithmetic.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_timearithmetic.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_timestamparithmetic.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_datearithmetic.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_timearithmetic.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_timestamparithmetic.html

list of valid tokens is provided in the message. Onlythose tokens that fit are listed. The error might beearlier in the statement, but the syntax of thestatement appears to be valid up to this point.


User responseCheck the SQL statement in the area of the indicatedkeyword. A colon or SQL delimiters might be missing.Correct the SQL statement.

Severity8 (error)

DSNH203I W csectname LINE nnnn COL ccSTATEMENT REFERENCESCOLUMN column name, WHICH ISDECLARED IN MORE THAN ONE OFTHE SPECIFIED TABLES

ExplanationThe column column name was referenced withoutsufficient qualification. Type checking cannot be done.


User responseIf the table declares are correct and the column nameis not unique, this creates an error in the BIND step.Correct the DECLARE TABLE statement, or use thecorrect table name to qualify the column name.

Severity4 (warning)

DSNH204I W csectname LINE nnnn COL ccSTATEMENT REFERENCESUNDECLARED TABLE table-name

ExplanationThe table definition was not provided. It is optional,but checking cannot be done without the tableinformation. (BIND checks against the actual tableduring later processing.)


Severity4 (warning)

DSNH205I W csectname LINE nnnn COL ccCOLUMN column-name WAS NOTDECLARED IN TABLE table-name

ExplanationThe column name column-name is not contained in thetable declarations. The name specified in a DISTINCTfunction must reference a column of the table. Thevalue expression of an ALL function must reference acolumn of the table.


User responseIf the table declares are correct and the column nameis not in the table, this creates an error in the BINDstep. Correct the DECLARE TABLE statement or thecolumn name.

Severity4 (warning)

DSNH206I W csectname LINE nnnn COL ccSTATEMENT REFERENCESCOLUMN column name WHICH ISNOT DECLARED IN THESPECIFIED TABLE(S)

ExplanationThe column column name is not contained in anyTABLE declaration for the tables specified in thestatement.


System programmer responseCheck the spelling of the column name. Ensure that allthe tables needed were specified in the statement.


User responseIf the table declares are correct and the column nameis not in the tables, this creates an error in the BINDstep. Correct the DECLARE TABLE statements or thecolumn name.

Severity4 (warning)

DSNH207I E csectname LINE nnnn COL ccILLEGAL ORDERBYSPECIFICATION

ExplanationIf the select expression involves a UNION operator, theORDER BY list must use numeric constants rather thanvariables.



Severity8 (error)

Related conceptsQueries (Db2 SQL)Related referenceorder-by-clause (Db2 SQL)fullselect (Db2 SQL)

DSNH251I E csectname LINE nnnn COL ccTOKEN name IS NOT VALID

ExplanationThe location name cannot contain alphabeticextenders for national languages (that is, #, @, and $in the United States).


User responseCorrect the content of the location name.

Severity8 (error)

DSNH270I FUNCTION NOT SUPPORTED

ExplanationThe statement cannot be processed because itviolates one or more of the following restrictions:

• DESC is not allowed in CREATE INDEX if the index isan XML index or expression-based index.

• RANDOM is not allowed in CREATE INDEX if theindex is an XML index or expression-based index.

• STACKED is not allowed on GET DIAGNOSTICS forexternal SQL procedures

• A FETCH statement cannot include WITH CONTINUEor CURRENT CONTINUE within an SQL routine.

• The only options allowed for ALTER FUNCTION ALLVERSIONS are SECURED and NOT SECURED. Anyother option is flagged with an error.


User responseCorrect the violation and issue the statement again.

Severity8 (error)

DSNH290I E csectname LINE nnnn COL cc NOVALID 'END DECLARE SECTION'FOUND

ExplanationThe user's source program contains a BEGIN DECLARESECTION, but no corresponding END DECLARESECTION was found.


User responseCheck the application program and ensure that a validEND DECLARE SECTION statement is present.

Severity8 (error)



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_orderbyclause.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_fullselect.html

DSNH291I E csectname LINE nnnn COL cc NOVALID 'BEGIN DECLARE SECTION'FOUND

ExplanationThe user's source program contains an END DECLARESECTION, but no corresponding BEGIN DECLARESECTION was found.


User responseCheck the application program and ensure that a validBEGIN DECLARE SECTION is present.

Severity8 (error)

DSNH292I E csectname LINE nnnn COL ccHOST NAME name IS TOO LONG;MAXIMUM IS size CHARACTERS

ExplanationFully qualified C host variable names cannot containmore than 256 characters.

System actionIf the containing SQL statement is executable, it isreplaced by host language statements that will, ifexecuted, set an error code in the SQLCA.

User responseReduce the length of names or the level ofqualification of the host variable name in error.

Severity8 (error)

DSNH303I W csectname LINE nnnn COL ccSTATEMENT SELECTSINCOMPATIBLE DATA TYPE INTOhostvar

ExplanationThe data type of host variable hostvar is notcompatible with the apparent type of thecorresponding select expression. One of them isnumeric and the other is character, or one of them ischaracter and the other is graphic. If the select

expression is a column reference, the data type isobtained from its declaration.


System programmer responseEnsure that the table definitions are current, and thatthe host variable has the proper data type.

User responseEnsure that the table definitions are current and thatthe host variable has the proper data type.

Severity4 (warning)

DSNH310I W csectname LINE nnnn COL cclanguage HOST VARIABLE nameWAS DECLARED IN location

ExplanationHost variable name should not be declared in thislocation of the source program. This message is issuedonly at reference time.


User responseIf this host variable is used, the user assumesresponsibility for possible exposure of incorrectoutput.

Declaring a COBOL host variable in the File Sectionmight lead to incorrect output from SQL statements orabend 04E with RC=00E7000C.

Severity4 (warning)

Related conceptsHost variables (Db2 Application programmingand SQL)Related tasksDeclaring host variables and indicator variables(Db2 Application programming and SQL)Related information00E7000C (Db2 Codes)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_hostvariablearraystructure.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_hostvariablearraystructure.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_declarehostvar.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00e7000c.html

DSNH312I E csect-name LINE line-numberCOL column-number UNDEFINEDOR UNUSABLE HOST VARIABLEvariable-name

ExplanationA problem occurred with the specified variable in anSQL statement. Either no declaration was found in theapplication program before the statement, or theattributes of the variable are improper for the intendeduse.


line-numberThe line number in the source code of theapplication program.

column-numberThe numeric representation of the column. Thefirst column is identified as column 1, the secondas column 2, and so on.

variable-nameThe name of the variable that caused the error.

This message is issued only at reference time.

System actionIf the SQL statement that contains the variable is adeclaration, it is discarded.

If the SQL statement that contains the variable isexecutable, it is replaced by host language statementsthat, if executed, set an error code in the SQLCA.

User responseCheck the declaration and the attributes of the namedhost variable. If you intended the name to refer to acolumn, the colon (:) must not be present. If youintended a literal, enclose the value in string delimiters(apostrophes or quotation marks).

If you intended to use a host variable, only a subset ofthe possible variable declarations are valid for use as aDb2 host variable. See the information about rules forhost variables in an SQL statement.

To determine the source of the problem, use the cross-reference listing and the source listing to determinewhether any of the following situations apply:

• If you use the STDSQL(YES) SQL processing option,make sure that all of the host variable declarationsare declared within the BEGIN DECLARE SECTIONand the END DECLARE SECTION.

• If the cross-reference listing does not contain thehost variable name, the declaration is missing. If thesource for a declaration is present, a missingterminator from a comment or from a string mightcause this type of error. The margin settings mightalso cause this type of error.

• If the name is present, but the data type is not listed,the host variable is not usable; it does not follow therules for valid host variable definitions.

• If several definitions exist for the name, the firstreference might occur before the definition. In thissituation, the TWOPASS SQL processing option helpsby processing DECLARE statements before the othertypes of statements. However, host variabledeclarations and cursor declarations are processedin the same pass. The host variables that arereferenced in cursor declarations must be definedbefore the cursor is defined in the applicationprogram. This rule applies regardless of whether theONEPASS or TWOPASS SQL processing option isused.

• A parameter marker is expected rather than a hostvariable in an EXECUTE IMMEDIATE statement.

• The data type of a host variable that is passed in aCALL statement is not CHAR or VARCHAR.

• The length attribute of a CHAR or VARCHAR hostvariable that is passed in a CALL statement exceeds255 characters.

• If you are using the precompiler for COBOL, checkwhether the named host variable is declared in astructure that contains FILLER elements. The FILLERelements might invalidate the variables in thestructure.

Severity8 (error)

Related conceptsUsing host variables in SQL statements (Db2Application programming and SQL)Output from the Db2 precompiler (Db2Application programming and SQL)Related tasksCollecting data for Db2 precompiler and Db2coprocessor problems (Collecting data)Related referenceDescriptions of SQL processing options (Db2Application programming and SQL)EXECUTE IMMEDIATE (Db2 SQL)DECLARE CURSOR (Db2 SQL)CALL (Db2 SQL)Host structures in COBOL (Db2 Applicationprogramming and SQL)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_hostvariablesqlstatement.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_hostvariablesqlstatement.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_outputprecompiler.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_outputprecompiler.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_cd4precompiler.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_cd4precompiler.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_descriptionprocessingoptions.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_executeimmediate.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_declarecursor.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_call.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_hoststructurescobol.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_hoststructurescobol.html

DSNH313I E csect-name LINE nnnn COL ccINVALID TYPE OR LENGTH OFHOST VARIABLE 'variable-name'

ExplanationThe host variable variable-name is used in an SQLstatement, but either the type or the length isimproper for this use.


User responseCheck the declaration and the attributes of the namedhost variable.

Severity8 (error)

Related conceptsCompatibility of SQL and language data types(Db2 Application programming and SQL)Related tasksDeclaring host variables and indicator variables(Db2 Application programming and SQL)

DSNH314I E csectname LINE nnnn COL ccREFERENCE TO HOST VARIABLEname IS AMBIGUOUS

ExplanationThe host variable name was defined more than once inthis application program. The precompiler cannotdistinguish which host variable definition should beused here. The following table indicates some possiblecombinations. Db2 supports only a single adjacentqualifier for a host variable name.

Case

Ref

Definition

Result SuggestedChange

1 a x.a Valid None

2 x.a x.a, y.a Valid None

3 a x.a, y.a DSNH314I Reference x.aor y.a

4 a x.a, a Valid None

5 x.a q.x.a,v.x.a

Noprecompiler

Variable namechanges

Case

Ref

Definition

Result SuggestedChange

error, buthostlanguagecompiler willissue anerror.

6 a a, a Noprecompilererror, buthostlanguagecompiler willissue anerror.

Variable namechanges

System actionIf the SQL statement is a declaration, it is discarded. Ifthe containing SQL statement is executable, it isreplaced by host language statements that will, ifexecuted, set an error code in the SQLCA.

User responseMake the host variable name unique or usequalification to indicate which host variable definitionis to be used, as suggested in the above table.

Severity8 (error)

DSNH330I E csect-name LINE line-numberCOL column-number TEXT COULDNOT BE CONVERTED TO CCSID1208, REASON reason-code

ExplanationDb2 parses SQL statements in Unicode UTF-8 (CCSID1208). The Db2 precompiler or coprocessor willconvert the application program internally (notexternally) from the application source EBCDIC CCSIDto UTF-8 for processing. This message indicates thattext from the application program could not beconverted.


reason-codeThe reason for the message or SQL code, indicatedby one of the following values:


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_compatibilitysqldatatype.html




012A character to be converted is an invalid code-point.

016The string to be converted does not conform tothe rules for valid data. For example, this couldbe a mismatch between shift-in and shift-out,or by the absence of half of a DBCS character.

System actionThe statement is discarded.

Programmer responseTake the appropriate action for the reason-code value:

012Change the text in the application program to avalid code point.

016Change the text in the application program toconform to the rules for well-formed mixed data.

Severity8 (error)

DSNH331I W csectname LINE nnnn COL cc.SUBSTITUTION OCCURRED ONCONVERSION FROM CCSID from-ccsid TO to-ccsid

ExplanationDuring conversion of the source text into UTF-8(CCSID1208), a character was encountered thatresulted in a substitution character of either '3F'x (inEBCDIC code pages), or '1A'x (in UTF-8).

System actionProcessing of the statement continues.

User responseReview the character that was converted to determineif the substitution character '3F'x is correct. If it iscorrect, the message can be ignored. Otherwise,change the character to the correct code point.

Severity4 (warning)

DSNH332I U csect-name CHARACTERCONVERSION FROM CCSID ccsid-1TO CCSID ccsid-2 IS NOT

SUPPORTED, REASON reason-number

ExplanationDb2 parses SQL statements in Unicode UTF-8 (CCSID1208). The Db2 precompiler or coprocessor willconvert the application program internally (notexternally) from the application source EBCDIC CCSIDto UTF-8 for processing. In some cases, Db2 alsoconverts portions from UTF-8 back to the sourceEBCDIC CCSID. This message indicates that theconversion could not take place.


ccsid-1The original CCSID.

ccsid-2The target CCSID.

reason-numberThe reason for the message, indicated by one ofthe following values:000

An invalid CCSID was specified on the CCSIDoption.

001No conversion is defined from the originalCCSID to the target CCSID

System actionThe precompiler or coprocessor is terminated.

System programmer responseMake sure that the Unicode System Servicesconversion image includes the required conversions.

User responseCheck that the value of the CCSID option is valid. Runthe precompilation again with a valid CCSID if you donot want to use the EBCDIC system CCSID.


Related conceptsz/OS Unicode Services User’s Guide andReference

DSNH350I E csect-name column-name WASIMPLICITLY OR EXPLICITLY


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.cunu100/abstract.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.cunu100/abstract.htm

REFERENCED IN A CONTEXT INWHICH IT CANNOT BE USED

ExplanationThe ALTER, CREATE, or DECLARE TEMPORARY TABLEstatement is invalid for one of the following reasons:DECFLOAT columns

A DECFLOAT column cannot be:

• Specified as a column of the primary key in aPRIMARY KEY clause.

• Specified as a column of a UNIQUE KEY.• Specified as a column of a foreign key in a

referential-constraint clause.• Specified as a column of a parent key in a

REFERENCES clause.• Specified as a column of a partitioning key for

range partitioning.• Defined in a table that has an EDITPROC.• Specified as a column of an index key.

Additionally, the result data type, including theintermediate result, of a key expression for anindex cannot be a DECFLOAT data type or adistinct type based on a DECFLOAT data type. Foran XML index, only XML columns can bespecified, and the result type of the index keycan be DECFLOAT.

LOB columnsA LOB column cannot be:





range partitioning.• Defined in a temporary table (created global

temporary table or declared global temporarytable).

• Defined in a table that has an EDITPROC.• Specified as a column of an index key• The result data type, including the intermediate

result, of a key expression for an index (thisincludes distinct types that are based on a LOB).

• The data type of a column in the result table ofan as-result-table clause of a CREATE TABLE orDECLARE GLOBAL TEMPORARY TABLEstatement.

• Defined in a table that has an edit procedure thatis defined with row attribute sensitivity.

security label columnsA security label column cannot be:

• Specified as a column of a foreign key in areferential-constraint clause.

• Specified as a column of a parent key in aREFERENCES clause.

• Specified in a key expression for an index.

A security label column column-name exists in theresult table of the as-result-table clause; however,it is not the only security label column in that resulttable. A table can be defined only with a singlesecurity label column.

XML columnsAn XML column cannot be:





range partitioning.• Defined in a temporary table (created global

temporary table or declared global temporarytable).

• Defined in a table that has an EDITPROC.• Specified as a column of an index key• The result data type, including the intermediate

result, of a key expression for an index.• The data type of a column in the result table of

an as-result-table clause of a CREATE TABLE orDECLARE GLOBAL TEMPORARY TABLEstatement.

• Defined in a table that has an edit procedure thatis defined with row attribute sensitivity.

hidden columnsA hidden column cannot be specified in a keyexpression for an index.

ROWID columnsA ROWID column cannot be the data type of acolumn in the result table of an as-result-tableclause of a CREATE TABLE or DECLARE GLOBALTEMPORARY TABLE statement.



User responseCorrect the syntax, and reissue the statement.

Severity8 (error)

DSNH372I E csectname ONLY ONE ROWID,ROW CHANGE TIMESTAMP,SECURITY LABEL OR IDENTITYCOLUMN IS ALLOWED IN A TABLE

ExplanationAn attempt was made to do one of the followingactions:

• Create a table with more than one ROWID column.• Add a ROWID column to a table that already has one.• Create a table with more than one identity column.• Add an identity column to a table that already has

one.• Add a security label column to a table that already

has one.• Create a table with more than one security label

column.• Create a table with more than one row change

timestamp column.• Add a row change timestamp column to a table that

already has one.• Create a table without a security label in the

Common Criteria environment which requires asecurity label column on every table created.


User responseFor a CREATE TABLE statement, select only onecolumn to have the row ID data type, the IDENTITYattribute, the SECURITY LABEL attribute, or the rowchange timestamp attribute. For an ALTER TABLEstatement, a ROWID column, identity column, orsecurity label column already exists for the table. Donot attempt to add another column with the data typerow ID, with the AS IDENTITY attribute or the ASSECURITY LABEL to the table. If the Common Criteriaenvironment is set (DSN6SPRM COMCRIT= YES), thenevery table created must have a security label.Designate a column AS SECURITY LABEL or changethe subsystem parameter.

Severity8 (error)

DSNH385I ASSIGNMENT TO AN SQLSTATE ORSQLCODE VARIABLE IN AN SQLPROCEDURE routine-name MAY BEOVER-WRITTEN AND DOES NOTACTIVATE ANY HANDLER

ExplanationSQL routine routine-name was created, but it containsan assignment statement that specifies the SQLCODEor SQLSTATE variable as the target. Assignment to anSQLSTATE or SQLCODE variable in an SQL routine onlychanges the value in the variable, and does notactivate any handler. The SQLSTATE and SQLCODEvariables are assigned values by processing of SQLstatements in the SQL routine. Therefore, any valueassigned might be over-written as a result of SQLstatement processing.

System actionThe routine definition is processed successfully.

Programmer responseNo recovery is necessary. If the intent was to signal anerror or warning, specify the SIGNAL or RESIGNALstatement instead of the assignment. To prevent thiswarning, remove any assignments to the SQLSTATE orSQLCODE special variables.

Severity4 (warning)

DSNH401I W csectname LINE nnnn COL ccSTATEMENT SPECIFIESINCOMPATIBLE OPERANDS FORCOMPARISON OPERATOR name

ExplanationThe comparison operation name is used with a mixtureof incompatible data type operands.


User responseMake both operands compatible character data types.Ensure that the table declaration is correct.


Severity4 (warning)

DSNH402I W csectname LINE nnnn COL ccSTATEMENT APPLIES name TOCHARACTER DATA

ExplanationThe numeric operation or function name is used with anon-numeric operand.


User responseMake the operand numeric or use a character function.Ensure that the table declaration is correct.

Severity4 (warning)

DSNH405I E csectname THE NUMERICCONSTANT constant CANNOT BEUSED AS SPECIFIED BECAUSE ITIS OUT OF RANGE

ExplanationThe numeric constant is not in the proper range.

The proper ranges for SQL values are as follows:

• 5.4E-79 to 7.2E+75 for FLOAT values• -(1031 -1) to +(1031 -1) for DECIMAL values• -2147483648 to 2147483647 for INTEGER values• -32768 to +32767 for small integer (SMALLINT)

values• -9.999999999999999x10-383 to

9.999999999999999x10384 for DECFLOAT(16)values

• -9.999999999999999999999999999999999x10-6143 to9.999999999999999999999999999999999x106144 for DECFLOAT(34) values

• - 9223372036854775808 to+9223372036854775807 for big integer (BIGINT)values

System actionIf the containing SQL statement is a declaration, it isdiscarded. If the containing SQL statement is

executable, it is replaced by host language statementsthat will, if executed, set an error code in the SQLCA.

User responseCorrect the number.

Severity8 (error)

DSNH408I W csectname LINE nnnn COL ccSTATEMENT INSERTS ORUPDATES COLUMN column-nameWITH INCOMPATIBLE DATA TYPE

ExplanationThe data type of the value to be inserted into a columnby an INSERT or UPDATE statement is incompatiblewith the declared data type of the column.


nnnnThe line number that is generated for DSNHmessages. For more information about these linenumbers, see “Message line numbers” on page165.

ccThe location of the source column. For moreinformation about the cc value, see “Message linenumbers” on page 165.

column-nameThe name of the column into which you are tryingin insert data.


Programmer responseEnsure that the table definitions are current. Also,ensure that host variables and literals have the properdata types for the target column.

Severity4 (warning)

Related conceptsCompatibility of SQL and language data types(Db2 Application programming and SQL)Related tasksDeclaring table and view definitions (Db2Application programming and SQL)




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_declaretableviewdefinition.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_declaretableviewdefinition.html

DSNH414I E csectname LINE nnnn COL cc THENUMERIC OR DATETIME COLUMNcolumn-name IS SPECIFIED IN ALIKE PREDICATE

ExplanationColumn column-name with a numeric data type wasspecified in a LIKE predicate. Columns specified in aLIKE predicate must be character or graphic stringcolumns.


User responseCorrect the statement.

Severity8 (error)

DSNH434I OPTION keyword IS ADEPRECATED FEATURE

Explanationkeyword is a deprecated feature that will not besupported in releases following Db2 11. It issupported, but it is best to discontinue the use of thiskeyword.

For indexes, we recommend that you use type 2indexes rather than type 1 indexes.

System actionProcessing continues normally.

User responseNo change is required for the current release.However, we recommend that you change your SQLstatement to remove this feature to prepare for futurereleases when this feature is not supported.

Severity4 (warning)

DSNH435I E csectname AN INVALIDSQLSTATE sqlstate IS SPECIFIEDIN A RAISE_ERROR FUNCTION,

RESIGNAL STATEMENT, ORSIGNAL STATEMENT

ExplanationThe SQLSTATE specified in the RAISE_ERRORfunction, RESIGNAL statement, or SIGNAL statementof a trigger or a routine does not conform to the rulesfor a valid SQLSTATE.


User responseCorrect the SQLSTATE specified in the RAISE_ERRORfunction or SIGNAL or RESIGNAL statement. TheSQLSTATE must be a character string containingexactly 5 characters. It must be of type CHAR definedwith a length of 5, or a type VARCHAR defined with alength of 5 or greater. The SQLSTATE value must followthe rules for application-defined SQLSTATEs asfollows:

• Each character must be from the set of digits ('0'through '9') or non-accented upper case letters ('A'through 'Z').

• The SQLSTATE class (first two characters) cannot be'00' since this represents successful completion.

Severity8 (error)

DSNH449I W csectname LINE nnnn COL ccCREATE FUNCTION ORPROCEDURE FOR routine-nameCONTAINS AN INVALID FORMATOF THE EXTERNAL NAME CLAUSEOR IS MISSING THE EXTERNALNAME CLAUSE

ExplanationAn error was found in the EXTERNAL NAME clause ofthe CREATE FUNCTION or CREATE PROCEDUREstatement for name, or the clause is needed but wasnot specified. See SQLCODE -449 for specificinformation about rules for LANGUAGE JAVA.



User responseCorrect the syntax of the CREATE or ALTER statementfor the function or procedure.

Severity8 (error)

Related referenceALTER FUNCTION (external) (Db2 SQL)ALTER PROCEDURE (external) (Db2 SQL)CREATE FUNCTION (external scalar) (Db2 SQL)CREATE PROCEDURE (SQL - external)(deprecated) (Db2 SQL)Related information-449 (Db2 Codes)

DSNH451I THE data-item DEFINITION IN THECREATE OR ALTER STATEMENTFOR routine-name CONTAINSDATA TYPE type WHICH IS NOTSUPPORTED FOR THE TYPE ANDLANGUAGE OF THE ROUTINE

ExplanationAn error was found in the data-item part of the CREATEor ALTER statement for routine-name. The statementcontained an invalid data type, or it contained adistinct type which is based on the invalid data type.


Programmer responseCorrect the specification of the routine and reissue theCREATE statement.

Severity8 (error)

DSNH457I E csectname LINE nnnn COL cc. AFUNCTION OR DISTINCT TYPECANNOT BE CALLED name SINCEIT IS RESERVED FOR SYSTEM USE.

ExplanationThe user-defined function or distinct type cannot becreated or referenced because the name selected isreserved for use by the system.

A number of names used as keywords are reserved forsystem use. These names may not be used as user-

defined functions or distinct-type-names, even if theyare delimited identifiers. These names are:

= < > >= <=<> ¬= ¬> ¬>ALL AND ANY BETWEEN DISTINCTEXCEPT EXISTS FALSE FOR FROMIN IS LIKE MATCH NOTNULL ONLY OR OVERLAPS SIMILARSOME TABLE TRUE TYPE UNIQUEUNKNOWN


User responseSelect a name for the function or distinct type that isnot reserved for system use.

Severity8 (error)

DSNH473I E csectname LINE nnnn COL cc. AUSER DEFINED DATA TYPECANNOT BE CALLED THE SAMENAME AS A SYSTEM PREDEFINEDTYPE (BUILT-IN TYPE).

ExplanationThe name of a data type to be created has anunqualified name that is the same as a system-predefined data type. This is not allowed. Addingdelimiters does not make the name valid. Thefollowing names are restricted:

BIGINT DECIMAL REF

BINARY DECFLOAT ROWID

BLOB DOUBLE SMALLINT

BOOLEAN DOUBLEPRECISION

TIME

CHAR FLOAT TIMESTAMP

CHAR VARYING GRAPHIC VARBINARY

CHARACTER INT VARCHAR

CHARACTERVARYING

INTEGER VARGRAPHIC

CLOB LONG VARCHAR XML

DATALINK LONGVARGRAPHIC

DATE NUMERIC

DBCLOB REAL


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_alterfunctionexternal.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_alterprocedureexternal.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createfunctionexternalscalar.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createproceduresqlexternal.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createproceduresqlexternal.html


DEC ROWID


User responseCorrect the statement to use another identifier for thename of the new user-defined type.

Severity8 (error)

DSNH487I E csectname LINE nnnn COL ccobject-type object-nameATTEMPTED TO EXECUTE AN SQLSTATEMENT WHEN THEDEFINITION OF THE FUNCTIONOR PROCEDURE DID NOT SPECIFYTHIS ACTION

ExplanationSQL procedure object-name contains SQL statements,but the SQL procedure definition specifies the NO SQLoption.

System actionThe SQL statement cannot be executed.

Programmer responseChange the definition of the SQL procedure to allowSQL statements, or remove the failing SQL statementfrom the SQL procedure.

DSNH490I E csectname LINE: MV.NNNN COLcc NUMBER number DIRECTLYSPECIFIED IN A SQL STATEMENTIS OUTSIDE THE RANGE OFALLOWABLE VALUES IN THISCONTEXT (minval, maxval)

ExplanationA number (number) was specified that is not valid inthe context in which it was specified. The minimumallowed value in this context is minval. The maximumallowed value in this context is maxval. n must bewithin the range specified by minval and maxval(minval =< n =< maxval).

System actionThe statement was not executed.

User responseChange the value n to a valid value in the statement.

Severity8 (error)

DSNH491I E csectname LINE nnnn COL cc.CREATE STATEMENT FOR USER-DEFINED FUNCTION function-name MUST HAVE A RETURNSCLAUSE, AND EITHER THEEXTERNAL CLAUSE (WITH OTHERREQUIRED KEYWORDS) OR THESOURCE CLAUSE.

ExplanationA required clause is missing in the CREATE for functionfunction-name. If EXTERNAL was specified, thefollowing must also be specified:

• LANGUAGE• PARAMETER STYLE



Severity8 (error)

DSNH504I E csectname LINE nnnn COL ccCURSOR name WAS NOTDECLARED

ExplanationIdentifier name is used as a cursor, but was notdeclared. The declaration might have been discardedbecause of errors.


User responseCorrect or add the required cursor declaration.


Severity8 (error)

DSNH506I E csectname LINE nnnn COL ccDECLARE CURSOR FORSTATEMENT NAME MUSTPRECEDE THE PREPARESTATEMENT FOR THATSTATEMENT NAME

ExplanationThis DECLARE name CURSOR statement is precededby a PREPARE name statement. In Db2, declarationsmust precede action statements. This is not the sameas in SQL/DS.

System actionThe declaration is noted as being in error anddiscarded.

User responseMove the DECLARE or PREPARE statement so thatthey are in the proper order, or specify the TWOPASSoption if the host language is PLI, ASM, or C. TheTWOPASS option has the precompiler check fordeclarations on the first pass and avoids this problem.

Severity8 (error)

DSNH520I E csectname THE OPENSTATEMENT FOR CURSOR cursor-name IS INVALID BECAUSE THECURSOR WAS DEFINED BY ANALLOCATE CURSOR STATEMENT

ExplanationThe cursor was not successfully declared, so it wasassumed to be defined by an ALLOCATE CURSORstatement. A cursor defined by an ALLOCATE CURSORstatement is open after successful completion of thestatement. Attempting to OPEN an allocated cursor isan error.


User responseAdd or fix the declaration of the cursor. If the cursor issupposed to be defined by an ALLOCATE CURSORstatement then remove the OPEN statement.

Severity8 (error)

DSNH521I W csectname THE statement FORCURSOR cursor-name ISASSUMED TO APPLY TO ADYNAMIC ALLOCATE CURSORSTATEMENT.

ExplanationA FETCH, CLOSE, or DESCRIBE for an undeclaredcursor was issued. The cursor is assumed to bedefined using a dynamic ALLOCATE CURSORstatement.

System actionThe cursor is assumed to be allocated dynamically.

User responseEnsure that the cursor in the FETCH, CLOSE, orDESCRIBE statement is dynamically allocated.

Severity4 (warning).

DSNH522I E csectname DESCRIBE CURSORcursor-name IS INVALID BECAUSETHE CURSOR WAS DEFINED BY ADECLARE CURSOR STATEMENT.

ExplanationDESCRIBE CURSOR is allowed for cursors definedusing the ALLOCATE CURSOR statement.


User responseRemove the DESCRIBE CURSOR statement. Issue aDESCRIBE of the statement used to define thedeclared cursor.

Severity8 (error).

DSNH527I WARNING: THE PRECOMPILER ORDB2 COPROCESSOR ATTEMPTEDTO USE THE DB2-SUPPLIEDDSNHDECP MODULE.


ExplanationThe DSNHDECP module that is supplied by Db2 isbeing used to run the Db2 precompiler or coprocessor.The precompiler or coprocessor requires site-dependent settings that are specified in theDSNHDECP module that was created when Db2 wasinstalled. The installation-generated DSNHDECPmodule typically resides in the SDSNEXIT library.

System actionProcessing halts.

System programmer responseThe following actions are required to enable the DSNHCLIST to load your user-supplied DSNHDECP modulerather than the Db2 DSNHDECP module that wassupplied by Db2:

1. The JOBLIB or STEPLIB concatenation of any job orTSO userid that calls DSNH needs to allocate thelibrary where the user-supplied DSNHDECP moduleresides (usually prefix.SDSNEXIT) ahead of thelibrary where the Db2-supplied DSNHDECP moduleresides (prefix.SDSNLOAD).

2. The DSNH call should include the PCLOADparameter, and it should be coded as shown here:PCLOAD('*(DSNHPC)').

User responseCheck the STEPLIB, JOBLIB, or system link listconcatenation used in the Db2 address spaces. Toensure that the proper DSNHDECP module is used,verify that the library that contains the DSNHDECPmodule that is generated during installation precedesthe SDSNLOAD library that contains the DSNHDECPmodule that was supplied by Db2.

DSNH557I E csectname LINE nnnn COL ccINCONSISTENT GRANT/REVOKEKEYWORD keyword; PERMITTEDKEYWORDS ARE keyword-list

ExplanationThe identified keyword is not permitted. The keyword-list is a list of the keywords that are permitted in thiscontext. The combination of privileges requested on aGRANT or REVOKE statement is not allowed. Theauthorities must all be of one type and consistent withthe form of GRANT or REVOKE. REVOKE UPDATE(column list) is not allowed; only REVOKE UPDATE ispermitted.

System actionThe containing SQL statement is replaced by hostlanguage statements that will, if executed, set an errorcode in the SQLCA.


Severity8 (error)

Related referenceGRANT (Db2 SQL)REVOKE (Db2 SQL)Statements (Db2 SQL)

DSNH558I E csect-name LINE nnnn COL cccINVALID CLAUSE ORCOMBINATION OF CLAUSES ON AGRANT OR REVOKE

Explanation"PUBLIC AT ALL LOCATIONS" is invalid for non-tableprivilege GRANT or REVOKE statements. It is alsoinvalid for table privilege GRANT or REVOKEstatements that specify the ALTER or INDEX privilege.



Severity8 (error)

Related referenceGRANT (Db2 SQL)REVOKE (Db2 SQL)Statements (Db2 SQL)

DSNH562I THE SPECIFIED PRIVILEGESCANNOT BE GRANTED TO PUBLIC.

ExplanationThe GRANT statement attempted to grant one of thefollowing privileges to the reserved authorization IDPUBLIC (public):

• System DBADM


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_grant.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_revoke.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_revoke.html


• DATAACCESS• ACCESSCTRL• CREATE_SECURE_OBJECT

These privileges cannot be granted to PUBLIC (public).

System actionThe statement is not processed.

Programmer response:Change the statement to specify a privilege that can begranted to PUBLIC, or specify a grantee other thanPUBLIC.

Related referenceGRANT (Db2 SQL)

DSNH577I E csectname LINE nnnn COL ccobject-type object-nameATTEMPTED TO MODIFY DATAWHEN THE DEFINITION OF THEFUNCTION OR PROCEDURE DIDNOT SPECIFY THIS ACTION

ExplanationAn SQL procedure contains SQL statements thatmodify data, but the SQL procedure is defined with theNO SQL, READS SQL DATA, or CONTAINS SQL option.


User responseChange the definition of the SQL procedure to allowSQL statements that modify data, or remove the failingSQL statement from the SQL procedure.

Severity8 (error)

DSNH580I E csectname LINE nnnn COL cc THERESULT-EXPRESSIONS OF A CASEEXPRESSION CANNOT ALL BENULL

ExplanationThere is a CASE expression in the statement that hasall the result-expressions (expressions following theTHEN and ELSE keywords) coded with the keywordNULL.

System actionThe statement was not processed.

Programmer responseChange the CASE expression to include at least oneresult-expression with a keyword other than NULL.

Severity8 (error)

DSNH581I E csectname LINE nnnn COL cc THEDATA TYPES OF THE RESULT-EXPRESSIONS OF A CASEEXPRESSION ARE NOTCOMPATIBLE

ExplanationA CASE expression in the statement has at least oneresult-expression (expressions following the THEN andELSE keywords) whose data type does not match thatof one of the other result-expressions.


Programmer responseChange the CASE expression so that the data types ofall of the result-expressions are compatible.

Severity8 (error)

DSNH582I E csectname LINE nnnn COL cc THESEARCH-CONDITION IN ASEARCHED-WHEN-CLAUSECANNOT BE A QUANTIFIEDPREDICATE, IN PREDICATE, ORAN EXISTS PREDICATE

ExplanationThe search-condition in a searched-when-clausespecifies a quantified predicate, an IN predicate or anEXISTS predicate, but is not allowed.


Programmer responseCorrect the search-condition.

Severity8 (error)



DSNH585I W csectname LINE nnnn COL ccDUPLICATE schema nameSCHEMA NAME

ExplanationThe identified schema name was specified twice in thestatement.

System actionThe duplicated schema name is ignore.

User responseRemove/correct the duplicate specification.

Severity4 (error)

DSNH586I E csectname LINE nnnn COL cc.THE TOTAL LENGTH OF THECURRENT PATH SPECIALREGISTER CANNOT EXCEED 254CHARACTERS.

ExplanationThe CURRENT PATH special register is defined as aVARCHAR(254). The content of the string includeseach schema name delimited with double quotes andseparated from the next schema name by a comma.The total length of the string of all schema names inthe CURRENT PATH cannot exceed 254 characters. ASET CURRENT PATH statement causing this messagewould exceed this limit.


User responseRemove schema names to reduce the total length to fitthe 254 character maximum length. If all the schemanames are required, it may be necessary toconsolidate some user-defined functions so that fewerschema names are required for the CURRENT PATH.

Severity8 (error)

DSNH587I A list of item-references are not inthe same family.

ExplanationEach item-reference in the SET assignment statementis either a host-variable or a transition-variable. Thelist of item-references must be of the same family,meaning if one of the item-references is a transition-variable, then all of the item-references in the list mustbe a transition-variable. If the statement is used in thetriggered action of a CREATE TRIGGER statement,each item-reference must identify a transition variable.If the statement is used in any other context, eachitem-reference must identify a host variable.


User responseCorrect the syntax of the SQL statement andprecompile the program again. Refer to the Db2 SQLReference to information on the SET assignmentstatement.

Programmer responseCorrect the statement and execute it again.

Severity8 (error)

DSNH590I E csectname LINE nnnn COL ccNAME name IS NOT UNIQUE INROUTINE routine-name

ExplanationName name is a parameter, SQL variable, conditionname, or label in SQL procedure routine-name. name isnot unique.


User responseChange the name to make it unique within the routine.

Severity8 (error)

DSNH599I W csectname LINE nnnn COL cc.COMPARISON FUNCTIONS ARENOT CREATED FOR A DISTINCT


TYPE BASED ON A LONG STRINGDATA TYPE.

ExplanationComparison functions are not created for a distincttype based on a long string data type (BLOB, CLOB,DBCLOB, LONG VARCHAR, LONG VARGRAPHIC) sincethe corresponding function are not available for thesebuilt-in data types.



Severity4 (warning)

DSNH612I E csectname LINE nnnn COL cccolumn-name IS A DUPLICATECOLUMN NAME

ExplanationThe CREATE INDEX, CREATE TABLE, CREATE VIEW orALTER TABLE statement specifies the same 'column-name' for two (or more) columns of the index, table,view, or the UPDATE OF clause of a trigger definitionspecifies the same column name more than once.Column names must be unique within an index, atable, a view, or in the UPDATE OF clause of a triggerdefinition. A column cannot be specified in more thanone ALTER TABLE clause except if it is specified in anALTER COLUMN clause and ADD CHECK CONSTRAINTclause.


User responseCorrect the CREATE statement to specify uniquenames for each of the columns of the index, table,view, or the columns in the UPDATE OF clause of atrigger definition. Correct the ALTER statement tospecify unique names for each of the ALTER COLUMNclauses.

This error can also occur on CREATE TABLE when acolumn list of a PRIMARY KEY, FOREIGN KEY, orUNIQUE clause contains two or more occurrences ofthe same column name.

Severity8 (error)

DSNH628I E csectname LINE nnnn COL ccMUTUALLY EXCLUSIVE CLAUSESHAVE BEEN SPECIFIED.

ExplanationMutually exclusive clauses were specified in one ormore ways.

• A column-definition value contains both NOTNULL and DEFAULT NULL clauses.

• A column-definition value contains bothFIELDPROC and DEFAULT clauses.

• A select-statement value contains both theupdate-clause and the FOR FETCH ONLY clause.

ALTER FUNCTION or CREATE FUNCTION statements

• A CREATE FUNCTION statement contains both aCAST FROM clause and a SOURCE clause.

• A CREATE FUNCTION statement contains both aSOURCE clause and a RETURNS TABLE clause.

• A CREATE FUNCTION statement contains both aSOURCE clause and a clause used to define anexternal function (EXTERNAL, LANGUAGE, NOSQL).

• A CREATE FUNCTION or ALTER FUNCTIONstatement contains a clause other than the CASTFROM clause for external scalar functions.

ALTER INDEX or CREATE INDEX statements

• A CREATE INDEX statement contains bothGENERATE KEY USING and a column specifiedas ASC or DESC.

• A CREATE INDEX statement contains both aGENERATE KEY USING clause, and a columnspecified as ASC or DESC.

• A CREATE INDEX or ALTER INDEX statementattempted to specify either CLUSTER,PARTITION BY, or both, for an XML index or anextended index.

• A CREATE INDEX or ALTER INDEX statementattempted to specify either CLUSTER,PARTITION BY, or both, for an XML index or anextended index.

ALTER PROCEDURE or CREATE PROCEDUREstatements

• A CREATE PROCEDURE or ALTER PROCEDUREstatement attempts to use the NO WLMENVIRONMENT and PROGRAM TYPE SUBoptions. When NO WLM ENVIRONMENT is used,then PROGRAM TYPE MAIN must also be used.


• A CREATE PROCEDURE or ALTER PROCEDUREstatement attempts to use both NO WLMENVIRONMENT and either USER or DEFINER forEXTERNAL SECURITY. When NO WLMENVIRONMENT is used, then PARAMETER STYLEmust be either GENERAL or SIMPLE CALL WITHNULLS.

• A CREATE PROCEDURE or ALTER PROCEDUREstatement contains both a LANGUAGE REXXclause, and a PARAMETER STYLE DB2SQL orPARAMETER STYLE JAVA clause.

ALTER TABLE statements

• An ALTER TABLE statement contains both aDROP CONSTRAINT clause and either a DROPFOREIGN KEY clause or a DROP CHECK clause.

• An ALTER TABLE statement contains both anALTER COLUMN clause and a VALIDPROC clause.

• An ALTER TABLE statement contains both anALTER COLUMN clause and a clause other thanthe check constraint clause.

• An ALTER TABLE statement contains a clauseand one of the following clauses: ADD CLONE,DROP CLONE, RENAME COLUMN, ADDORGANIZED BY HASH, ALTER ORGANIZATION,or DROP HASH ORGANIZATION. When one ofthese clauses is specified, no other clause isallowed on the ALTER TABLE statement.

ALTER TABLESPACE or CREATE TABLESPACEstatements

• A CREATE TABLESPACE or ALTER TABLESPACEcontains both the LOCKPART YES and LOCKSIZETABLESPACE

• A CREATE TABLESPACE or ALTER TABLESPACEcontains both the LOCKPART YES and LOCKSIZETABLESPACE

• A CREATE TABLESPACE statement contains boththe SEGSIZE and NUMPARTS clauses

• A CREATE TABLESPACE statement contains boththe SEGSIZE and LARGE clauses.

• A CREATE TABLESPACE statement contains boththe SEGSIZE and MEMBER CLUSTER clauses.

CREATE TRIGGER statements

• A CREATE TRIGGER statement specifies morethan one correlation name for OLD, NEW,OLD_TABLE, or NEW_TABLE. Each of thesecorrelation specific can appear no more thanonce in the CREATE TRIGGER statement.

DECLARE CURSOR statements

• A DECLARE CURSOR statement specifies boththe WITH RETURN TO CLIENT option and one

the following options: WITH RETURN (TOCALLER) or WITHOUT RETURN.


Programmer responseChange the options specified in the statement andreissue the statement.

Severity8 (error)

DSNH630E E csectname LINE nnnn COL cc THEWHERE NOT NULLSPECIFICATION IS INVALID FORTYPE 1 INDEXES

ExplanationType 1 indexes cannot be created with the WHERENOT NULL specification.


Programmer responseEither the index must be created as a type 2 index, orthe WHERE NOT NULL specification must not be used.

Severity8 (error)

DSNH637I E csectname LINE nnnn COL ccDUPLICATE keyword KEYWORD

ExplanationThe identified keyword was specified twice in thestatement.


User responseRemove the duplicate specification.


Severity8 (error)

DSNH643I A CHECK CONSTRAINT OR THEVALUE OF AN EXPRESSION FOR ACOLUMN OF AN INDEX EXCEEDSTHE MAXIMUM ALLOWABLELENGTH

ExplanationThe definition of a check constraint or expression of anindex column exceeds the maximum allowable lengthfor one of the following reasons:

• A check constraint exceeded 3800 UTF-8 bytes.Redundant blank spaces are excluded from thislimit.

• A value for an expression or an index exceeded 4000UTF-8 bytes.

System actionThe CREATE TABLE or ALTER TABLE statement failed.The statement cannot be executed.

User responseChange the constraint or expression so that it does notexceed the maximum allowable limit. If i is a checkconstraint, rewrite the check constraint definition sothat it is less than 3800 UTF-8 bytes. You might needto divide the check constraint into two or more smallercheck constraints.

Severity8 (error)

DSNH644I E csectname INVALID VALUESPECIFIED FOR KEYWORDkeyword-name IN statement-typeSTATEMENT

ExplanationThe value specified for the keyword-name parameterin the statement-type SQL statement is not a permittedvalue.

System actionIf the SQL statement containing the problem is adeclaration, it is discarded. If the SQL statementcontaining the problem is executable, it is replaced byhost language statements that will, if executed, set anerror code in the SQLCA.

User responseCorrect the statement.

Severity8 (error)


DSNH683I E csectname LINE nnnn COL cc.THE SPECIFICATION FORCOLUMN, DISTINCT TYPE,FUNCTION, OR PROCEDURE data-item CONTAINS INCOMPATIBLECLAUSES

ExplanationThere is an error in the data item specification in astatement. Incompatible specifications are presentsuch as "INTEGER and FOR BIT DATA", or "INTEGERAS LOCATOR". The location of the error is given bydata-item as follows:

• For a CREATE or ALTER TABLE statement, data-itemgives the name of the column containing the error.The error could be an invalid specification of FOR BITDATA, FOR SBCS DATA, FOR MIXED DATA, orFIELDPROC for column data-item.

• For a CREATE FUNCTION or CREATE PROCEDUREstatement, data-item is a token that identifies thearea of the problem in the statement. For example,"PARAMETER 3", "RETURNS", or "CAST FROM".

• For a CREATE DISTINCT TYPE statement, data-itemgives the name of the type being defined

• Otherwise, data-item is a token that identifies thearea of the problem in a parameter list for a function.For example, "PARAMETER 5".



Severity8 (error)

DSNH684I E csectname LINE nnnn COL ccLENGTH OF LITERAL LISTBEGINNING string IS TOO LONG



ExplanationThe length of the literal list beginning with string,excluding insignificant blanks and delimitingparenthesis, is greater than 255.


System programmer responseCorrect the SQL statement.

Severity8 (error)

Related conceptsConstants (Db2 SQL)Language elements (Db2 SQL)

DSNH739I E csectname LINE nnnn COL cc.CREATE FUNCTION function-nameFAILED BECAUSE FUNCTIONSCANNOT MODIFY DATA WHENTHEY ARE PROCESSED INPARALLEL.

ExplanationThe function cannot be created because ALLOWPARALLEL and MODIFIES SQL DATA were bothspecified explicitly or implicitly. A function cannot beparallelized if it modifies data.


User responseSpecify DISALLOW PARALLEL or change the MODIFIESSQL DATA to NO SQL, CONTAINS SQL or READS SQLDATA.

Severity8 (error)

DSNH740I xxxxxx phase FINISHED, RC =retcode, LISTING IN data-set

ExplanationThe DSNH INST phase completed with return coderetcode. The phase is one of the following:

• PLI Macro Pass

• Precompiler• CICS Command Translator• Bind Package• Bind Plan• Compile/assembly• PLI• Prelink (unique to C/370 Compiler)• Link• Run

If the CLIST puts the listing into a data set, the nameof the data set is shown as data-set. If the PRINTparameter is LEAVE, NONE, or TERM, the 'LISTING INdata-set' part of this message is omitted.

Refer to message DSNH756I for an explanation of theprint data set names assigned during processing.

This message is issued by the following CLIST: DSNH

System actionProcessing continues as requested.

User responseThis phase is complete. If there are errors, othermessages are produced. The next phase requestedbegins. The order of the phases is:

1. PLI Macro Pass2. Precompiler3. CICS Command Translator4. Bind Package5. Bind Plan6. ASM, ASMH, C (C/370 Compiler), COBOL, COBOL2,

FORTRAN, PLI7. Prelink8. Link9. Run

Severityretcode

DSNH741I process1(NO) IMPLIES THATprocess2 CANNOT BE RUN

ExplanationAn inconsistent processing set was specified. Anearlier phase and a later phase were requested, butnot the intermediate step needed to process databetween them. For example, requesting theprecompile and the link edit without the compiler


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_constantsintro.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_langelementsoverview.html

produces this error. Values for process1 are PRECOMP,CICSXLAT, COMPILE, LINK, or BIND. Values forprocess2 are COMPILE, LINK, or RUN.


System actionprocess2 is not performed, but other processing isdone.

User responseSpecify a consistent combination of processing.Application program preparation needs to run all thesteps to provide a correct application program. Theprocess does allow beginning or ending steps to be runat a different time. See message DSNH740I for therequired step order.

Severity4 (warning)

DSNH750I INVALID DATA SET: clist-keywordclist-keyword-parameter

ExplanationThe data set name specified on the clist-keyword-parameter contains unbalanced parenthesis.


System actionThe CLIST is terminated.

User responseIf a member name is to be associated with thespecified data set, the member name must beenclosed in parentheses.

Severity8 (error)

DSNH751I clist ERROR IN parameter VALUEvalue

ExplanationThe specified CLIST keyword parameter does not havean acceptable value.

System actionThe CLIST processing is terminated.

User responseCorrect the invalid parameter, and resubmit the job.

Severity8 (error)

Related tasksCompiling and link-editing an application (Db2Application programming and SQL)Related referenceDSNH (TSO CLIST) (Db2 Commands)

DSNH752I INPUT DATA SET NAME ISMISSING OR NONE

ExplanationThe DSNH CLIST requires a value for the input data setname (INPUT). You cannot use an input data set nameof NONE.


System actionThe CLIST prompts for a name, if prompting is allowed.If prompting is not allowed, for example in batch orwhen PROFILE NOPROMPT was entered, the CLISTterminates.

User responseSpecify an INPUT name. See message DSNH753I.

Severity0 (successful)

DSNH753I ENTER INPUT DATA SET NAME

ExplanationThe CLIST is requesting the name of the input data set.


System actionThe system waits for user to enter data set name or forthe CLIST to be terminated.

User responseEnter the name of the data set. Do not specify theparameter or command, but just enter the name of thedata set. The standard TSO prefixing will be done if thedata set name is not entered within apostrophes.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_compilelinkeditapp.html



Severity0 (successful)

DSNH754I clist OUTNAME PARAMETER nameMUST NOT CONTAIN SPECIALCHARACTERS

ExplanationThe DSNH and DSNHC CLISTs, clist, use the OUTNAMEparameter to build names for a number of data setsthat are passed from phase to phase. These names areprefixed by an authorization ID or TSO prefix value andhave a number of suffixes. For this reason, OUTNAMEparameter name must not contain special characters.It can contain a period or national characters. Itcannot have apostrophes to specify a single data setname.


User responseCorrect the input request. The default for thisparameter is TEMP, which should be adequate formost usage.

Severity8 (error)

DSNH755I OUTNAME PARAMETER nameMUST NOT BEGIN THE SAME ASINPUT input

ExplanationThe DSNH CLIST uses the OUTNAME parameter nameto build a number of data sets that are passed fromphase to phase. These data sets could conflict with theINPUT data set (input) if the names are the same,causing the INPUT data set to be overwritten. To avoidthis problem, the names are not allowed to have thesame initial characters.



User responseCorrect the input request. Specify a differentOUTNAME. The default for OUTNAME is TEMP.

Severity8 (error)

DSNH756I clist PRINT PARAMETER nameMUST NOT CONTAIN SPECIALCHARACTERS

ExplanationThe DSNH and DSNHC CLISTs (clist) use the PRINTparameter to build names for data sets used for theprint listings from various phases. These names areprefixed by an authorization ID or a TSO prefix valueand have a number of suffixes. The PRINT parametername can contain a period or national characters, butit cannot contain special characters. It cannot haveapostrophes to specify a single data set name.

The data set names built using the PRINT(print)qualifier are the following:print.CXLIST

CICS Command Translatorprint.LINKLIST

Linkage Editorprint.LIST

Compiler or Assemblerprint.PCLIST

Db2 Precompilerprint.SYSCPRT.LIST

C/370 Compilerprint.SYSOUT.PRELLIST

C/370 Prelink Utility

System actionThe CLIST terminates.

User responseCorrect the name specified with the PRINT parameter.

Severity8 (error)

DSNH757I ERROR IN PLAN NAME LENGTHvalue

ExplanationThe value is too long for a plan name. A plan name hasa maximum of 8 characters.




User responseSpecify a plan name with 8 or fewer characters.

Severity8 (error)

DSNH758I HOST(host-language) IS NOTPERMITTED WITH RUN(IMS) ORRUN(CICS)

ExplanationThere is no facility for connecting a FORTRAN programto either IMS or CICS.



User responseUse the specified language in the TSO or batchenvironment.

Severity8 (error)

DSNH759I clist TERMINATING, phase RC =retcode

ExplanationThe DSNH or DSNHC clist terminated at phase becausethe return code retcode was greater than or equal tothe RCTERM parameter value.


User responseDetermine the cause for the high return code. If theparameters include TERM(NONE) and direct the PRINTto a data set, you might need to search the print datasets for the listing of the error. Refer to messageDSNH756I for an explanation of the print data setnames assigned during processing.

Problem determinationThe location of the messages describing the priorerrors depends upon the values of the TERM andPRINT parameters. The messages can be directed tothe terminal, to preallocated data sets, or to data setsdynamically allocated during CLIST processing.

If TERM(NONE) PRINT(NONE) was specified, themessages are not available. Execute the CLIST againand specify a location for the error messages.

To find the documentation, note the immediatelypreceding DSNH740I message for the location of thelistings. If the 'LISTING IN data-set' portion of themessage is missing, specify a PRINT data set,SOURCE(YES) and XREF(YES), and execute the CLISTagain. Use TERM(TERM) to direct error messages toyour terminal. These listings and execution of theDSNH CLIST are required for problem diagnosis.

If the error is in the CLIST or the error location is CLISTCHECKING, use CONTROL(SYMLIST) to produce adetailed trace of the CLIST execution and provide thetrace listing.

Check for DSNH751I messages that describe the error.

Severityretcode

DSNH760I PRELINK OPTION INVALID WITHHOST LANGUAGE (host-language)

ExplanationInvocation of the PRELINK step is not supported byhost-language. This option is only valid for thefollowing DSNH HOST language compilers: C, CPP, andIBMCOB.


System actionThe DSNH PRELINK parameter is ignored and prelinkutility processing is bypassed. Clist processingcontinues normally with a return code of 4.


Severity4 (error)

Related tasksCompiling and link-editing an application (Db2Application programming and SQL)





DSNH794I W csectname LINE nnnn COL cc.THE OBJECT object-name CANNOTBE CREATED BECAUSE THE FIRSTTHREE CHARACTERS ARERESERVED FOR SYSTEM OBJECTS

ExplanationIn general, SYS is a reserved prefix for names. The onlyexceptions to this rule include the followingconditions:

• SYSADM and SYSTOOLS are valid schema names.• SYSPROC is a valid schema name for stored

procedures.• SYSIBM is a valid schema name for a stored

procedure when the current application process hasthe SYSADM or SYSCTRL privilege.

• SYSTOOLS is a valid schema name when the currentapplication process has the SYSADM or SYSCTRLprivilege.

This message is also issued if an attempt is made togrant the CREATEIN, ALTERIN or DROPIN privileges ona schema with the SYS prefix. The same exceptionsapply to the grant.

This condition is similar to the condition reported inSQLCODE -20074.

User responseSelect a name that does not start with a reservedprefix.

Severity4

DSNH867I E csectname LINE nnnn COL cc.INVALID SPECIFICATION OF AROWID COLUMN

ExplanationFor a CREATE TABLE statement, the specification of aROWID column might be invalid for one of thefollowing reasons:

• A ROWID column cannot be a column of a temporarytable.

• A ROWID column cannot be a column of a table withan EDITPROC.

• A ROWID column cannot be a column of a foreignkey.

• A ROWID column cannot be a column of a primarykey.

• A ROWID column cannot be referenced in the check-condition of a table check constraint.

System actionThe statement was not executed.


Severity8

DSNH901I S csectname U LINE nnnn COL ccINTERNAL PRECOMPILER OR DB2COPROCESSOR ERROR - REASONCODE ccc

ExplanationAn internal compiler consistency check failed. Thefollowing list contains the possible reason codes:000

The message formatter was called with an unlistedinternal message number.

001The parser received a token code of 0 from thelexical scan. Lexical scan refers to a scan of wordsrather than syntax.

002Error in storage suballocation control blocks.

• The error might have occurred because a Db2SQL statement limitation was exceeded. The SQLstatement might be referencing, creating, ordeclaring more columns than the Db2 definedmaximum number allowed for an SQL statement.Another possibility is that too many hostvariables are being referenced in the SQLstatement.

003Error in a storage suballocation request.

• This error might have occurred because ofstorage constraints when building the DBRMentry for the SQL statement or because the SQLstatement exceeds the Db2 maximum statementlength.

004Error in pointer structures.

005On BIND or REBIND, a host variable was not found.



006Unexpected value for parser option.

007The size of a DBRM entry exceeds the maximumsize.

008Internal conversion error.

• An error occurred when converting a timestampversion-id.

System actionThe precompiler or coprocessor is terminatedimmediately.



Problem determinationA copy of the application program source and theprintout is useful (specify SOURCE and XREF).


DSNH902I U csect-name SEVERE INTERNALPRECOMPILER OR DB2COPROCESSOR ERROR INCONVERSION FROM CCSID ccsid-1TO CCSID ccsid-2, REASONreason-number

ExplanationDb2 parses SQL statements in Unicode UTF-8 (CCSID1208). The Db2 precompiler or coprocessor willconvert the application program internally (notexternally) from the application source EBCDIC CCSIDto UTF-8 for processing. In some cases, Db2 alsoconverts portions from UTF-8 back to the sourceEBCDIC CCSID. This message indicates that a severeerror has occurred in the internal conversion.


ccsid-1The original CCSID.

ccsid-2The converted CCSID.

reason-numberThe reason for the message, indicated by one ofthe following values:001

The buffer used as part of the interfacebetween the Db2 coprocessor and the hostlanguage compiler is too small for theconversion. This reason code can be returnedwhen certain special registers are referencedin your query, and Db2 converts them in thisbuffer, such as CURRENT SERVER andCURRENT PACKAGESET. If the problem isencountered because of references to a specialregister, try assigning the value of the specialregister to a host variable and then replacereferences to the special register in your querywith a reference to the host variable. Forexample:

1. SET :HV = CURRENT SERVER2. Update your query to replace references to

CURRENT SERVER with :HV

002An invalid code point was found duringconversion.

003The string being converted does not conform tothe rules for valid data.

004A miscellaneous error occurred on conversion.

System actionThe precompiler or coprocessor is terminatedimmediately.



Problem determinationA copy of the application program source and theprintout is useful. Specify SOURCE and XREF.







DSNH904I csectname U STORAGE OVERFLOW

ExplanationMore storage is needed, but could not be obtainedduring precompiler/parser execution.

System actionThe precompiler/parser is terminated immediately.

System programmer responseThe storage required for the current statement couldnot be acquired or exceeds the maximum for a singlerequest. If the region size is being used completely,check whether the region can be expanded. If itcannot be expanded, the SQL statement is too large tobe processed.


DSNH1760I E csectname LINE nnnn COL cc.CREATE STATEMENT FOR STOREDPROCEDURE procedure-nameMUST HAVE A VALID LANGUAGECLAUSE AND EXTERNAL CLAUSE.

ExplanationThe CREATE statement for procedure procedure-namemust have both a valid LANGUAGE clause and a validEXTERNAL clause.



Severity8 (error)

DSNH4001I HOST LANGUAGE STATEMENTEXCEEDS MAXIMUM OF 1000LINES

ExplanationA PL/I program contains a declaration that coversmore than 1000 source lines and contains a LOBvariable declaration.


User responseSplit the DCL statement into two parts.

Severity8

DSNH4408I E csectname LINE nnnn COL cc THEVALUE IS NOT COMPATIBLE WITHTHE DATA TYPE OF ITS TARGET

ExplanationThe data type of the value to be assigned to theparameter or SQL variable is incompatible with thedeclared data type of the assignment target. Bothmust be:

• Numerals• Characters• Graphics• Dates or character• Times or character• Timestamps or character• Row ID's• The same distinct types


User responseExamine the current definition for the parameter orSQL variable and ensure that it has the proper datatype.

Severity8 (error)

DSNH4700I E csect-name LINE line-numberCOL column-number ATTEMPT TOUSE NEW FUNCTION BEFORENEW FUNCTION MODE


ExplanationAn attempt was made to use syntax for functions thatare newer than the version that is specified by the SQLprocessing option NEWFUN.


line-number and column-numberThe location of the error in the source program.

When NEWFUN(NO) is specified, you cannot usesyntax for functions that are introduced by the currentversion of Db2. When NEWFUN(V9) is specified, youcannot use syntax for any functions that wereintroduced after Version 9. When the value ofNEWFUN(V8) is specified, you cannot use syntax forany functions that were introduced after Version 8.


Programmer responseCheck the value of the SQL processing option settingfor NEWFUN. If the NEWFUN option is not specified,then the installation default value is used.

Do one of these things:

• Restrict your program to functions that earlierreleases of Db2 introduced. These functions areallowed regardless of the value of NEWFUN.

• Process your program with a value of YES for theNEWFUN option. However, you cannot BIND theDBRM until New Function Mode has been enabled.

Severity8 (error)

Related conceptsImplications of falling back (Db2 Installationand Migration)Application defaults parameters (Db2Installation and Migration)Related tasksMigrating from enabling-new-function mode* tonew-function mode (Db2 Installation andMigration)Related referenceDescriptions of SQL processing options (Db2Application programming and SQL)

Related information-4700 (Db2 Codes)

DSNH4701I S csectname OPTION: optionOPTION NOT PERMITTED WITHNEWFUN NO

ExplanationYou cannot use the indicated SQL processing optionwhen the SQL processing option NEWFUN has a valueof NO.


Programmer responseTo prevent this error in the future, take one of thefollowing actions:

• Restrict your precompilation to options that wereintroduced in earlier releases of Db2. These optionsare valid regardless of the value of NEWFUN.

• Process your program with a value of YES for theNEWFUN option.


DSNH4702I column IS NOT VALID IN THECONTEXT WHERE IT IS USED

ExplanationThe specified column is not a column of the table orview that was specified as the object of the UPDATE orINSERT operation.

System actionThe statement cannot be executed. No data wasupdated.

Programmer responseVerify that the column and table names are specifiedcorrectly in the SQL statement. If a correlation name isspecified for a table or view, verify that subsequenttable references of the table or view in qualifiedcolumn names use the correlation name and not thetable or view name.

SQLSTATE42703


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_fallbackimplications.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_fallbackimplications.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsnhdecpparamsds.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_convertenfmst2nfm.html






DSNH4760I THE DB2 SQL COPROCESSOR ISUSING THE LEVEL nnn INTERFACEUNDER DB2 VERSION db2-version

ExplanationThis message specifies the level of the Db2 SQLcoprocessor that is in use. This message is for IBMsoftware support.

System actionNo action required.

User responseNo action required.


DSNH4761I THE DB2 SQL COPROCESSOR HASCHANGED THE NEWFUN OPTIONVALUE FROM YES TO NO

ExplanationThe Db2 SQL coprocessor option NEWFUN(YES) wasspecified, but the level of the Db2 SQL coprocessorinterface is not compatible with NEWFUN(YES).Therefore, the Db2 SQL coprocessor is running withNEWFUN(NO). Functions that are specific to the newversion of Db2 are not allowed.

System actionNo action required.

User responseUpgrade to a later compiler version that supports thenew Db2 functions.

Severity4 (warning)

DSNH4762I W csectname LINE nnnn COL ccSQL OPTIONS REQUIRE NEWERCOMPILER

ExplanationThe Db2 SQL coprocessor was used duringcompilation of a Db2 application. One or more of thefollowing SQL options were specified:

• STDSQL(YES)

• TWOPASS

The level of the compiler that was used does notsupport those SQL options.


User responseIf the SQL options are required, upgrade to a newerlevel of the compiler.

Refer to message DSNH4760I in the output listing andthe Db2 Program Directory for information on selectingthe correct level of the compiler to use.

If the SQL options are not required, remove them.

Severity4 (warning)

DSNH4763I E csect-name LINE nnnn COL ccSQL TYPE IS CLAUSE WASINCORRECTLY SPECIFIED

ExplanationThe SQL TYPE IS clause was incorrectly specified in aDb2 application that was prepared with the Db2 SQLcoprocessor.


User responseCorrect the statement syntax.

Severity8 (error)

Related conceptsDifferences between the Db2 precompiler andthe Db2 coprocessor (Db2 Applicationprogramming and SQL)Compatibility of SQL and language data types(Db2 Application programming and SQL)Related tasksProcessing SQL statements by using the Db2coprocessor (Db2 Application programming andSQL)Related referenceEquivalent SQL and Fortran data types (Db2Application programming and SQL)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_differenceprecompilercoprocessor.html





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_processsqlstmtcoprocessor.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_equivalentfortrandatatypes.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_equivalentfortrandatatypes.html

DSNH4770I E csect-name SQLFLAGPRECOMPILER OPTION IS NOLONGER SUPPORTED

ExplanationFederal Information Processing Standards (FIPS) andSAA flagging support is disabled. You can no longerspecify the precompiler option SQLFLAG.

System actionPrecompiler ends with a return code of 8.

User responseRemove the SQLFLAG precompiler option.

Severity8 (error)

DSNH4771I E csectname PRECOMPILEROPTION QUOTE CANNOT BESPECIFIED IN THIS CONTEXT.USE THE APOST OPTION

ExplanationWhen the value of the CCSID precompiler option is1026 or 1155, and the value of the HOST precompileroption is IBMCOB, the APOST precompiler option mustbe used because the precompiler modified sourcedefines the quotation mark with the hex point of 'FC'X,which is not taken by the COBOL compiler.


User responseSpecify the APOST precompiler options, andprecompile the application again. There is no need tomodify the COBOL source.

Severity8 (error)

DSNH4772I I csect-name LINE line-numberCOL column-numberUNQUALIFIED IDENTIFIERidentifier-name IS USED IN ANAMBIGUOUS CONTEXT

ExplanationThe identifier that is indicated by identifier-name is nota unique reference in the SQL statement context.



identifier-nameThe non-unique identifier. An sql-parameter or sql-variable with the same name is declared, but itdoes not have priority over a column with thisname in this context.


User responseInspect the ambiguous reference, and qualify thenamed identifier to clarify the intended usage in theSQL statement.

• For a reference to an SQL parameter, qualify thename with the SQL PL routine name.

• For a reference to an SQL variable, qualify the namewith the label of the compound statement thatdeclares the variable. If no label is present in thecompound statement, add one.

• For a reference to a column, qualify the name withthe appropriate table designator.


DSNH4773I W csect-name LINE line-numberCOL column-number HANDLERBODY IS A CONTROL STATEMENTOTHER THAN A COMPOUNDSTATEMENT

ExplanationThe body of a handler declaration is an SQL controlstatement other than an SQL compound statement.



This usage causes the original condition informationavailable to the condition handler logic to be displacedin the following manner:


• The SQL diagnostic area accessed by a GETCURRENT DIAGNOSTICS statement will be modifiedand unrelated to the original condition.

• The values of variables SQLSTATE and SQLCODE willbe modified and unrelated to the original condition.


User responseReplace the SQL control statement (IF, CASE, LOOP,REPEAT, WHILE) that defines the body of the handlerdeclaration with an SQL compound statement(BEGIN).

Severity4 (warning)

DSNH4775I E csect-name LINE line-numberCOL column number STATEMENTSPECIFIED IN SQL ROUTINE ISNOT ALLOWED WITHIN ACOMPOUND STATEMENT

ExplanationA statement specified in the routine body is notallowed in a compound statement.



An ATOMIC compound statement cannot be specified:

• In an SQL scalar function.• In an SQL procedure.• Within another compound statement that is defined

as ATOMIC.


User responseRemove the statement from the SQL routine.

Severity8 (error)

DSNH4777I E csectname LINE nnnn COL ccNESTED COMPOUND STATEMENTSNOT ALLOWED

ExplanationAn SQL procedure contains nested compoundstatements, which are not allowed.


User responseRewrite the SQL procedure body so that it does notcontain nested compound statements.

Severity8 (error)

DSNH4778I E csect-name LINE line-numberCOL column number END LABELlabel-name NOT SAME AS BEGINLABEL

ExplanationAn SQL routine statement contains an ending label anda beginning label that do not match.



label-nameThe name given for the ending label.


User responseChange the ending label in the statement to match thebeginning label.

Severity8 (error)

DSNH4779I csectname LINE nnnn COL ccLABEL label SPECIFIED statementIS NOT VALID


ExplanationIn an SQL procedure, label is specified on a GOTO orLEAVE statement. label is not defined or is not a validlabel for the statement.

The label on a LEAVE statement must be the label for aLOOP, REPEAT, WHILE, or compound statement.

The label in a GOTO statement must be defined withina scope that the GOTO statement can reach.

• If the GOTO statement is defined in a compoundstatement, label must be defined inside the samecompound statement.

• If the GOTO statement is defined in a handler, labelmust be defined in the same handler and mustfollow the other scope rules.

• If the GOTO statement is defined outside a handler,label must not be defined within a handler.


User responseChange the label in the LEAVE statement to match thelabel on the LOOP, REPEAT, WHILE, or COMPOUNDstatement that contains the LEAVE statement.

Ensure that the label in the GOTO statement is definedwithin a scope that the GOTO statement can reach.

Severity8 (error)

DSNH4780I E csect-name LINE line-numberCOL column number UNDOSPECIFIED FOR A HANDLER

ExplanationIn an SQL routine, UNDO is specified for a handler,which is not supported.




User responseChange the UNDO handler to a CONTINUE or EXIThandler.

Severity8 (error)

DSNH4781I E csect-name LINE line-numberCOL column number CONDITIONcondition-name SPECIFIED INHANDLER NOT DEFINED

ExplanationA handler is declared for a condition in an SQL routine,but the routine does not contain a conditiondeclaration statement that defines the condition.



condition-nameThe name of the condition that is not defined.


User responseInclude a condition declaration statement in the SQLroutine that relates the condition name to anSQLSTATE value.

Severity8 (error)

DSNH4782I E csect-name LINE line-numberCOL column number A CONDITIONOR SQLSTATE condition-valueSPECIFIED IS NOT VALID

ExplanationAn SQL routine specified a condition value that is notvalid.

condition-valueEither a specific condition value, which is providedas an SQLSTATE value, or a general conditionvalue, such as SQLEXCEPTION, SQLWARNING, orNOT FOUND.

The condition or SQLSTATE value is not valid for one ofthe following reasons:


• The handler declaration or condition declarationspecifies an SQLSTATE value that is not valid.

• The condition or SQLSTATE value has already beenspecified by another handler in the same scope.

• The condition or SQLSTATE was specified in thesame handler as SQLEXCEPTION, SQLWARNING, orNOT FOUND.


User responseCorrect the condition or SQLSTATE value.

Severity8 (error)

DSNH4783I E csectname LINE nnnn COL ccSELECT LIST FOR CURSOR cursor-name IN FOR STATEMENT NOTVALID

ExplanationAn SQL procedure contains a FOR statement in whichthe select list in the cursor declaration has a columnthat is not valid. That column is a duplicate of anothercolumn in the select list, or the column is not named.


User responseEnsure that all columns in the select list for a cursordeclaration in a FOR statement are unique and arenamed. If a column of the select list is the result of acolumn function, specify an AS clause to name thecolumn.

Severity8 (error)

DSNH4784I E csect-name DSNHDECP IS FORDB2 VERSION "dsnhdecp-version"BUT product-name IS FOR DB2VERSION "dsnhdecp-version"

ExplanationThe release information from the given DSNHDECPmodule or user-supplied application defaults module

does not match the current level of the Db2precompiler or SQL coprocessor.

System actionThe precompiler or SQL coprocessor is terminated.

Programmer responseEnsure that a dsnhdecp data-only load module for thecorrect Db2 version is available to the precompiler orSQL coprocessor, and that dsnhdecp load module isthe one that Db2 finds first. Db2 searches forthedsnhdecp module in the following places, and inthe following order:

• The STEPLIB concatenation for the precompile orcompiler step for SQL coprocessor

• The JOBLIB concatenation for the job that includesthe precompile step or compiler step for SQLcoprocessor

• The system link list


DSNH4785I E csect-name LINE line-numberCOL column number THEDECLARATION OR USE OF THESQLSTATE OR SQLCODE VARIABLEIS NOT VALID

ExplanationThe use of SQLCODE or SQLSTATE in an SQL routinebody is invalid for one of the following reasons:

• SQLCODE or SQLSTATE was specified as a parametername.

• SQLCODE is not declared as INTEGER in a return-codes-declaration clause.

• SQLSTATE is not declared as CHAR(5) in a return-codes-declaration clause.

• SQLCODE or SQLSTATE is assigned the value NULL.





User responseDeclare SQLSTATE only as CHAR(5) and SQLCODE onlyas INTEGER. Do not assign the null value to SQLCODEor SQLSTATE. Do not use SQLCODE or SQLSTATE asparameter names.

Severity8 (error)

DSNH4787I E csectname LINE nnnn COL ccRESIGNAL STATEMENT NOTWITHIN A HANDLER

ExplanationThe RESIGNAL statement can only be used insidecondition handlers.


User responseRemove the RESIGNAL statement or use a SIGNALstatement instead.

Severity8 (error)

DSNH4788I csectname CCSID ccsid FORPROGRAM SOURCE CODE IS NOTSUPPORTED

ExplanationThe Db2 precompiler or Db2 coprocessor does notaccept input source code with the specified CCSID.The rules for the CCSID are:

• When source code for an external SQL procedure isprecompiled, the CCSID must be a Latin-1 EBCDICCCSID.

• For other uses of the Db2 precompiler or Db2coprocessor, the CCSID must be an EBCDIC CCSID.

System actionThe precompiler or Db2 coprocessor terminates.

User responseSpecify an EBCDIC CCSID.


DSNH4789I csectname SQL PROCESSINGOPTION "option" IS IGNORED

ExplanationWhen using the Db2 precompiler or the Db2coprocessor, the SQL processing option option isignored.


User responseMake sure the correct CCSID is provided to theprecompiler or coprocessor.

If the CCSID provided is a single-byte CCSID, thenx'0E' and x'0F' characters are not interpreted as shift-out and shift-in characters surrounding DBCScharacters. If the CCSID provided is a mixed CCSID,then x'0E' and x'0F' characters are interpreted as shift-out and shift-in characters surrounding DBCScharacters.

The NEWFUN processing option is deprecated.

Related conceptsOptions for SQL statement processing (Db2Application programming and SQL)

DSNH4790I csect-name DSNHDECP HASEBCDIC CCSID ccsid IN EFFECT

ExplanationThis message indicates the CCSID that is specified inthe DSNHDECP MODULE. This CCSID is SCCSID if theMIXED DATA field is NO in DSNHDECP, or MCCSID ifthe MIXED DATA field is YES.


ccsidThe CCSID that is specified in the DSNHDECPmodule.

System actionNo action is required.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_optionssqlprocessing.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_optionssqlprocessing.html


Related conceptsApplication defaults parameters (Db2Installation and Migration)Related tasksSpecifying subsystem CCSIDs (Db2Internationalization Guide)

DSNH4791I csect-name CCSID ccsid-1 IS USEDTO PROCESS SQL, BUT DSNHDECPHAS EBCDIC CCSID ccsid-2 INEFFECT

ExplanationThe Db2 coprocessor is using CCSID ccsid-1 toprocess SQL. ccsid-1 is different from the ccsid-2,which was loaded from the DSNHDECP module.


ccsid-1The CCSID that was used to process SQLstatements.

ccsid-2The CCSID that was loaded from the DSNHDECPmodule. ccsid-2 is SCCSID if the MIXED DATA fieldis NO in DSNHDECP, or MCCSID if the MIXED DATAfield is YES.


User responseEnsure that the CCSIDs specified for compilation is theCCSID intended for processing SQL. Processing SQLwith a CCSID different from the CCSID used indatabase tables can lead to unexpected results. TheCCSID that is used to interpret data in host variablescan be from the DSNHDECP module, the ENCODINGBIND option, a CCSID specified on the DECLAREVARIABLE statement or specified as a compile optionsuch as CCSID0 for PL/I or SQLCCSID for COBOL.

Check the program listing for message DSNH527I,which was issued if the coprocessor is using the Db2-supplied DSNHDECP module. If it is not intended touse the Db2-supplied DSNHDECP module, refer to thedescription of DSNH527I to take corrective action.

Severity4 (warning)

Related tasksSpecifying a CCSID for your application (Db2Internationalization Guide)Specifying subsystem CCSIDs (Db2Internationalization Guide)Related informationDSNH527IWARNING: THE PRECOMPILER OR DB2COPROCESSOR ATTEMPTED TO USE THE DB2-SUPPLIED DSNHDECP MODULE.

DSNH4792I csect-name LINE line-number COLcolumn-number SQL STATEMENTWILL CAUSE AN ERROR IN BIND,REASON reason-code

ExplanationAn SQL statement that uses invalid syntax wasdetected by the precompiler or Db2 coprocessor. Thismessage does not terminate the compile, but bindingthe DBRM produced by this compile may result in anerror.


line-numberThe line number of the invalid SQL syntax.

column-numberThe column number of the invalid SQL syntax

reason-code

1. A SELECT INTO statement contains a UNION orUNION ALL set operator.

System actionThe invalid SQL is allowed in the compile.

User responsePlan to revise the SQL statement to remove the invalidsyntax.

Severity4 (warning)

Related referenceSELECT INTO (Db2 SQL)fullselect (Db2 SQL)




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/char/src/tpc/db2z_specifysubsystemccsids.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/char/src/tpc/db2z_specifyccsidapp.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/char/src/tpc/db2z_specifyccsidapp.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_selectinto.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_fullselect.html

DSNH4920I E csectname TOKEN ID ARRAYTOO SMALL

ExplanationThe Db2 coprocessor needs more token identifierarray entries than the coprocessor allocated.

System actionControl is returned to caller with no other action taken.

User responseAllocate a larger token identifier array and make thecall to SQLGCMPL again.

Severity8 (error)

DSNH5011I HOST VARIABLE ARRAY host-variable-array IS EITHER NOTDEFINED OR IS NOT USABLE

ExplanationHost-variable-array host-variable-array was specifiedin a multiple-row FETCH or multiple-row INSERTstatement. The host-variable array is not defined or isnot usable for one of the following reasons:

• The host variable is not a valid host-variable array.• The host variable is not a dimensioned array.• The host-variable array has more than 1 dimension.• The host-variable array defines a structure that does

not conform to the rules for defining a host-variablearray.

• The dimension of the host-variable array used forindicators is not equal to the dimension of the mainhost-variable array.


Programmer responseCorrect any of the following and precompile theprogram again. Ensure that:

• the dimension of the indicator variable array is equalto the dimension of the main host-variable array.

• the host-variable array is a single-dimensional array.• the host-variable array or host-indicator-variable

array do not contain structures that are notpermissible. The only structures that may be defined

in a host-variable array are those that are used todefine variable length string host variables.

Related conceptsHost-variable arrays (Db2 Applicationprogramming and SQL)Related tasksDeclaring host variables and indicator variables(Db2 Application programming and SQL)

DSNH5033I DECLARE VARIABLE NOT VALIDFOR variable

ExplanationHost variable variable specified in a DECLAREVARIABLE statement is not valid. The DECLAREVARIABLE statement occurs after any SQL statement(in a COBOL or FORTRAN application program) or aftera DECLARE CURSOR statement (in an applicationprogram in any other host language), where the SQLstatement and the DECLARE VARIABLE refer to thesame variable.


User responseEnsure that the DECLARE VARIABLE occurs before theuse of the host variable in an SQL statement in theapplication.

Severity8 (error)

DSNH5034I DECLARE VARIABLE NOT VALIDFOR variable

ExplanationHost variable variable specified in a DECLAREVARIABLE statement is not valid for one of thefollowing reasons:

• A reference is made to a variable that does not exist.• A reference is made to a variable that is a structure.• A reference is made to a variable that is a

component of two more structures.• The host variable is not defined as character,

varying-length character, graphic, varying-lengthgraphic, CLOB, or DBCLOB. In this case, CLOB ASLOCATOR or DBCLOB AS LOCATOR is not considereda CLOB or DBCLOB.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_hostvariablearray.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_hostvariablearray.html



• FOR BIT DATA, CCSID 65535, FOR MIXED DATA, FORSBCS DATA is specified and the variable is defined asgraphic, varying-length graphic, or DBCLOB.

• FOR BIT DATA, or CCSID 65535 is specified and thevariable is defined as CLOB.

System actionThe statement cannot be precompiled.

User responseCorrect the definition of the host variable. Precompilethe program again.

Severity8 (error)

DSNH5035I HOST VARIABLE variable ISSPECIFIED TWICE IN A DECLAREVARIABLE STATEMENT

ExplanationThe host variable variable was specified in two or moreDECLARE VARIABLE statements, or was specified twoor more times in one DECLARE VARIABLE statement. Ahost variable can be specified once at most in aDECLARE VARIABLE statement.


User responseSpecify the host variable at most once in a DECLAREVARIABLE statement.

Severity8 (error)

DSNH5036I CCSID VALUE OUT OF RANGE

ExplanationThe CCSID for a DECLARE VARIABLE or CASTstatement is outside the range 1 - 65533, or the value65535. The value must be within the range 1 - 65533,or the value must be 65535.


User responseIf this message is issued for a "DECLARE VARIABLECCSID integer"or "CAST CCSID integer" statement,change the value to be within the range 1 - 65533 orthe value 65535. If this message is issued for aDECLARE VARIABLE statement with the "FOR SBCSDATA" or "FOR MIXED DATA" clause, then the CCSIDsspecified on panel DSNTIPF at installation time needto be updated with valid values.

Severity8 (error)

DSNH5037I DECLARE VARIABLE STATEMENTFOUND WITH ONE-PASSPRECOMPILATION

ExplanationA DECLARE VARIABLE statement was found, but thesource program is being precompiled with only onepass. If a DECLARE VARIABLE is used in an assemblersource program, the ONEPASS precompiler optionmust not be used. If a DECLARE VARIABLE is used in aC, C++, or PL/I source program, the TWOPASSprecompiler option must be used.

System actionThe source program cannot be precompiled.

User responseSpecify the TWOPASS precompiler option or, forassembler, do not specify the ONEPASS precompileroption.

Severity8 (error)

DSNH20008I ATTEMPT TO USE UNSUPPORTEDFEATURE msg-token. REASONCODE: reason-code

ExplanationThe statement attempted to use a feature or formatthat is not supported.

msg-tokenText that identifies the unsupported feature.

reason-codeA numeric value that identifies the unsupportedfeature.


3TYPE 1 indexes are no longer supported. OnlyTYPE 2 can be specified, beginning in DB2Version 6.

4The DSETPASS keyword is no longersupported, beginning with DB2 Version 6.

System actionThe statement or EXPLAIN operation cannot beprocessed.

Programmer responseTake appropriate action based on the reason-codevalue. In most cases, remove references to theunsupported clause or keyword from the SQLstatement, to avoid using the unsupported feature.

SQLSTATE560A9

Severity8 (error)

Related conceptsFunction that Db2 11 no longer supports (Db2for z/OS What's New?)Related referenceDeprecated function in Db2 11 (Db2 for z/OSWhat's New?)Related information-20008 (Db2 Codes)+20520 (Db2 Codes)

DSNH20060I E csect-name LINE line-numberCOL column-identifierUNSUPPORTED DATA TYPE data-type ENCOUNTERED IN SQL object-type object-name

ExplanationAn unsupported data type was specified in thedefinition of an object.


line-number and column-identifierThe location of the definition.

data-typeThe data type that was specified. This data type isnot supported for SQL procedure parameters orvariables.

For native SQL procedures, you cannot use theROWID data type.

For external SQL procedures, you cannot use thefollowing data types:

• BINARY• VARBINARY• BIGINT• DECIMAL FLOAT• XML• ROWID• TIMESTAMP with precision• TIMESTAMP WITH TIME ZONE• Distinct type

object-typeThe type of object.




User responseChange the syntax to specify a supported data type.

Severity8 (error)

DSNH20061I E csectname LINE nnnn COL ccUNEXPECTED ERROR RETURNEDFROM LANGUAGE ENVIRONMENT:REASON CODE reason-code,RETURN CODE return-codemodule-name

ExplanationAn Language Environment® error occurred while theDb2 precompiler was processing an SQL procedure.The reason codes and associated return codes are:Reason code

Meaning and associated return code


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/wnew/src/tpc/db2z_functionsnotsuppfromv10.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/wnew/src/tpc/db2z_functionsnotsuppfromv10.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/wnew/src/tpc/db2z_deprecated.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/p20520.html

1No PIPI token. return-code is the return code fromthe CEEPIPI(init_sub) call.

2CEE could not be loaded. return-code is the returncode from the CEEPIPI(add_entry) call.

3PIPI would not terminate. return-code is the returncode from the CEEPIPI(term) call.

4Call to module-name failed. return-code is thereturn code from the CEEPIPI(call_sub) call.

5Bad response from PIPI. return-code is the returncode from module-name.

See the explanation of return codes for the appropriateCEEPIPI call in z/OS Language EnvironmentProgramming Guide for explanations of the LanguageEnvironment return codes.


User responseCorrect the condition that is described by reason-code.

Severity8 (error)

DSNH20111I E csect-name LINE line-numberCOL column number CANNOTISSUE SAVEPOINT, RELEASESAVEPOINT, ROLLBACK TOSAVEPOINT FROM A TRIGGER,FROM A USER-DEFINEDFUNCTION, OR FROM A GLOBALTRANSACTION

ExplanationAn invalid statement was issued.



The following statements cannot be used in the bodyof a trigger, global transaction, or user-definedfunction:

• SAVEPOINT• RELEASE SAVEPOINT

• ROLLBACK TO SAVEPOINT

System actionThe statement is not processed.

Programmer responseCorrect the logic of the application program so thatthis error does not occur.

Severity8 (error)

Related referenceSAVEPOINT (Db2 SQL)RELEASE SAVEPOINT (Db2 SQL)ROLLBACK (Db2 SQL)

DSNH20120I E csect-name LINE line-numberCOL column number AN SQL TABLEFUNCTION MUST RETURN A TABLERESULT

ExplanationAn SQL function that specifies TABLE in the RETURNSclause must return a result that is a table.




User responseEither remove the TABLE keyword from the RETURNSclause to make it a scalar function or specify afullselect in the RETURN statement of the TABLEfunction body.

Severity8 (error)

DSNH20129I E csectname LINE nnnn COL ccSPECIAL REGISTER IS NOT VALIDAS USED

ExplanationAn attempt was made to reference a special register,but the syntax was invalid for the special register.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_savepoint.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_releasesavepoint.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_rollback.html

The CURRENT PACKAGE PATH special register, or alocal special register such as CURRENT SERVER,CURRENT PACKAGESET, or CURRENT APPLICATIONENCODING SCHEME cannot be referenced in a SETassignment-statement statement or VALUES INTOstatement where:

• The special register is part of an expression in thesource value.

• Multiple source values are being assigned to multipletargets.

• The source value in an assignment is the CURRENTPACKAGE PATH special register or a local specialregister, and the target is an array variable.

If the target is not an array variable, the only valid usesof these special registers in a SET assignment-statement statement or VALUES INTO statement are:

• SET variable= CURRENT APPLICATION ENCODINGSCHEME;

• SET variable= CURRENT SERVER;• SET variable= CURRENT PACKAGESET;• SET variable= CURRENT PACKAGE PATH;• VALUES CURRENT APPLICATION ENCODING

SCHEME INTO variable;• VALUES CURRENT SERVER INTO variable;• VALUES CURRENT PACKAGESET INTO variable;• VALUES CURRENT PACKAGE PATH INTO variable;


Programmer responseCorrect the statement in one of the following ways:

• Do not use the special register in an expression asthe source value of a SET assignment-statement orVALUES INTO statement.

• Do not assign multiple values to multiple specialregisters in a SET assignment-statement or VALUESINTO statement.

• Do not assign a special register to a target that is anarray variable.

Severity8 (error)

DSNH20148I E csect-name LINE line-numberCOL column number A RETURNSTATEMENT DOES NOT EXIST ORWAS NOT INVOKED DURING THEEXECUTION OF ROUTINE routine-

name WITH SPECIFIC NAMEspecific-name

ExplanationThe SQL function must contain at least one RETURNstatement and a RETURN statement must be executedwhen the function is invoked.



routine-nameThe name of the routine.

specific-nameThe specific function name, which is unique withinthe schema.


User responseEnsure that a RETURN statement is executed when thefunction is invoked.

Severity8 (error)

DSNH20228I A STACKED DIAGNOSTICS AREAIS NOT AVAILABLE

ExplanationA stacked diagnostics area is only accessible fromwithin a handler in a native SQL routine.

This error can occur when the STACKED keyword isspecified in a GET DIAGNOSTICS statement outside ofan SQL procedure.

System actionThe statement was processed.

Programmer responseModify the application logic so that the STACKEDdiagnostic is only accessed from within a handler. Ifthe routine is an external SQL procedure, or a hostlanguage program then the STACKED keyword cannotbe used.


DSNH20289I INVALID STRING UNIT unitSPECIFIED FOR FUNCTIONfunction-name

ExplanationThe statement invoked a built-in function using a stringlength unit that is not valid with the type of data that isprovided to the function. This can occur for thefollowing reasons:

• Binary data was specified with unit. CODEUNITS16,or CODEUNITS32 are not valid with binary stringdata.

• Graphic data was specified with OCTETS as thestring length unit. OCTETS is not valid with graphicdata.


System programmer responseChange the invocation of the function to remove theinvalid string length unit specification or change it to avalid string length unit for the data type beingprocessed.

DSNH20367I W csectname LINE nnnn COL ccOPTION clause IS NOTSUPPORTED IN THE CONTEXT INWHICH IT WAS SPECIFIED

ExplanationThe clause in the statement is not supported in thecontext in which has been specified. The clause isignored.


User responseNo change is required for the current release; however,it is recommended that the statement be modified toconform to valid SQL syntax.

DSNH20428I E csect-name LINE line-numberCOL column-number, URISPECIFIED IN THE XMLSCHEMACLAUSE IS AN EMPTY STRING

ExplanationAn empty string was found in the XMLSCHEMA clause.



System actionThe SQL statement that contains the empty string isdiscarded.

User responseSpecify the URI in the correct format.

Severity8 (error)

DSNH20436I E csect-name LINE line-numberCOL column number THE DATATYPE SPECIFIED FOR AN ARRAYTYPE IS NOT VALID.

ExplanationThe data type that is specified for an array in one of thefollowing contexts is not valid:

• CREATE TYPE statement• Array constructor• Argument to UNNEST• Argument to ARRAY_AGG• Target of ARRAY_AGG

The following restrictions apply to the data type for anarray:

• These data types are not supported:

– ROWID– XML– A user-defined data type other than an array data

type• The data type for an array index of an associative

array must be INTEGER or VARCHAR, with a lengthattribute no greater than 32704.


Programmer responseUse a supported data type.


Severity8 (error)

Related referenceArray constructor (Db2 SQL)collection-derived-table (Db2 SQL)CREATE TYPE (Db2 SQL)

DSNH20441I E csect-name LINE line-numbertype-name TYPE IS NOT VALIDWHERE SPECIFIED. REASONCODE reason-code.

ExplanationAn array data type cannot be specified in the context inwhich it is used.

type-nameThe name of the array type.

reason-codeA numeric value that indicates the reason that thestatement cannot be executed. Possible valuesare:1

An array data type was specified where anarray type is not supported, or a value that isnot an array data type was specified where anarray value is required.

Some of the contexts in which an array datatype is supported are:

• A parameter to an SQL function• A return data type from an SQL function• A Parameter to an SQL procedure• An SQL variable that is declared in an SQL

function• An SQL variable that is declared in an SQL

procedure

Some of the contexts in which an array datatype is not supported are:

• A parameter or variable for an externalroutine

• A return type of an inline SQL function• A column in a table

The UNNEST operator must be an array value.That array value must be one of the followingitems:

• An SQL variable• An SQL parameter• An array function invocation

• A CAST specification of a parameter markerto an array type

2A global variable was defined as a distinct type.A global variable cannot be defined as adistinct type.


Programmer responseSee the documentation for the SQL statement onwhich the error occurred for a complete list ofrestrictions on the use of the array data type in thatcontext. Change the SQL statement to use an arraydata type only in a context in which it is allowed.

Severity8 (error)

Related referenceArray constructor (Db2 SQL)ARRAY_DELETE (Db2 SQL)TRIM_ARRAY (Db2 SQL)EXISTS predicate (Db2 SQL)ALTER TABLE (Db2 SQL)CREATE FUNCTION (external scalar) (Db2 SQL)CREATE FUNCTION (external table) (Db2 SQL)CREATE PROCEDURE (external) (Db2 SQL)CREATE TABLE (Db2 SQL)DECLARE GLOBAL TEMPORARY TABLE (Db2SQL)

DSNH20474I PERMISSION OR MASK CANNOTBE CREATED FOR object-name OFTYPE object-type. REASON CODEreason-code.

ExplanationThe CREATE PERMISSION or CREATE MASK statementfailed




A SELECT clause contains either * or name.*.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_arrayconstructor.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_collectionderivedtable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createtype.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_arrayconstructor.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_bif_arraydelete.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_bif_trimarray.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_existspredicate.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_altertable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createfunctionexternalscalar.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createfunctionexternaltable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createprocedureexternal.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createtable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_declareglobaltemptable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_declareglobaltemptable.html

14An ordinary SQL identifier contains a dash (-).


Programmer responseCorrect the syntax, and reissue the statement.

Related referenceCREATE MASK (Db2 SQL)CREATE PERMISSION (Db2 SQL)

DSNH20494I A PUBLIC ALIAS NAME, name,CAN ONLY BE QUALIFIED WITHSYSPUBLIC AND NOT THESCHEMA NAME schema-name.

ExplanationA qualified name was specified for a public alias butthe qualifier was not SYSPUBLIC.


User responseChange the two-part name to a one-part name orspecify the qualifier SYSPUBLIC. If a public alias wasnot intended and PUBLIC was specified in thestatement, remove the keyword PUBLIC.

DSNH20524I THE STATEMENT FAILED BECAUSEOF AN INVALID PERIODSPECIFICATION OR PERIODCLAUSE FOR PERIOD period-name.REASON CODE reason-code.

ExplanationA period specification or period clause is invalid.

period-nameThe name of the period that is invalid. Possiblevalues are BUSINESS_TIME or SYSTEM_TIME.

reason-codeA numeric value that indicates why the period isinvalid. reason-code can have the following value:

3period-name violated the followingrequirement: each expression must return avalue of a built-in data type and can containany of the following supported operands:

• A constant• A special register• A variable, which can be either a host

variable, an SQL variable, an SQL parameter,a transition variable, or a global variable

• A parameter marker• A CAST specification where the cast operand

is a supported operand• An expression that uses arithmetic operators

and operands• A scalar function whose arguments are

supported operands

These rules have the following exceptions:

• A period specification or period clause for aview must not contain an untyped parametermarker.

• The source expression of SET CURRENTTEMPORAL BUSINESS_TIME and SETCURRENT TEMPORAL SYSTEM_TIMEstatements must not contain a parametermarker or a transition variable.


User responseCorrect the syntax and resubmit the statement.

Severity8 (error)

Related conceptsData types (Db2 SQL)Variables (Db2 SQL)Related referenceSpecial registers (Db2 SQL)CAST specification (Db2 SQL)Scalar functions (Db2 SQL)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createmask.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_createpermission.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_datatypesintro.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_refs2variables.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_specialregistersintro.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_castspecification.html



Chapter 7. DSNI messagesMessage identifiers that begin with DSNI communicate information about the data manager.

DSNI001I RESTART HAS BEEN DEFERREDREASON reason-code TYPEresource-type NAME resouce-name

ExplanationRestart could not be performed for one or more pagesof the identified resource. Those pages are placed inthe logical page list (LPL) and restart for those pages isdeferred. The reason code explains why restart wasnot performed.

reason-codeThe reason that the restart failed.


System actionDb2 restart continues. Pages for which restart activitywas not performed are put into the LPL.

User responseCorrect the problem indicated by the reason code.Then use the START DATABASE command or theRECOVER utility to remove the pages from the LPL.

Related tasksRemoving pages from the logical page list (Db2Administration Guide)Deferring restart processing (Db2Administration Guide)Related reference-START DATABASE (Db2) (Db2 Commands)RECOVER (Db2 Utilities)

DSNI002I csect-name UNABLE TO STARTOBJECT TYPE object-type OBJECTNAME object-name REASONreason-code TYPE resource-typeNAME resource-name

ExplanationThe resource identified could not be started because itwas unavailable. The resource could be a database, atable space, an index space, or a partition within atable space or an index space.


object-type and object-nameThe type of object and the object name. If the Db2catalog is unavailable, 'object-type' contains binaryzeros and 'object-name' contains blanks.

reason-codeThe reason code that explains why the resourcewas unavailable


System actionThe specified database, space, or partition is notstarted and remains in its current state. If there areother databases, spaces, or partitions to be started,they are processed normally.

User responseCorrect the resource unavailable problem and reissuethe -START command.

DSNI003I csect-name UNABLE TO STOPOBJECT TYPE object-type OBJECTNAME object-name REASONreason-code TYPE resource-typeNAME resource-name

ExplanationThe identified object could not be stopped because aresource required to perform the stop was unavailable.The object could be a database, a table space, anindex space, or a partition within a table space or anindex space.


object-type and object-nameThe type of object and the object name. If the Db2catalog is unavailable, object-type contains binaryzeros and object-name contains blanks.

reason-codeThe reason code that explains why the resourcewas unavailable


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_removepagesfromlogicalpagelist.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_removepagesfromlogicalpagelist.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_deferrestartprocessing.html





System actionThe specified database, space, or partition is notstopped and remains in the current state. If there areother databases, spaces, or partitions to be stopped,they are processed normally.

User responseCorrect the resource unavailable problem and reissuethe -STOP command.

DSNI004I RESOURCE HAS BEEN STOPPEDTYPE resource-type NAMEresource-name

ExplanationThe identified resource could not be opened/closed,initialized, or was found to be in an inconsistent state.The resource has been stopped by Db2. If an openerror occurred during Db2 startup, restart processingfor the resource was deferred.


System actionThe database, table space or index space is stoppedby Db2.

User responsePrevious messages provide information to allow you todetermine the cause of the problem and the method ofcorrecting it. Refer to them, and correct the problem.Then restart the database, table space, or index spaceusing the -START command; and invoke theapplication again.

DSNI005I csect-name LPL OR GRECPRECOVERY CANNOT BE DONE FORfunction-name - ID = function-idOBJECT TYPE object-type OBJECTNAME object-name REASONreason-code TYPE resource-typeNAME resource-name

ExplanationResource recovery failed because of problems duringgroup buffer pool recovery pending (GRECP) or logicalpage list (LPL) recovery.


function-nameThe command or function that failed. Expectedvalues are:

• START DATABASE COMMAND• AUTOMATIC GRECP RECOVERY• AUTOMATIC LPL RECOVERY

function-idA decimal number that represents the recoveryfunction.


object-typeThe type of object, which could be a table space,an index space, or a partition within a table spaceor index space.

reason-codeA numeric value that indicates the reason for thefailure.


This message, in combination with message DSNI006Ior DSNI022I, provides the LPL or GRECP recoveryinformation for a recovery function that is identified bythe function-id.

System actionThe specified object is started but remains in a LPL orGRECP state. If there are other objects to berecovered, they are processed normally. Other statusmessages might be issued to the console, including:

• DSNI006I, which indicates the start of recovery• DSNI022I, which provides the status of recovery

operations• DSNI051I, which indicates that second pass log

apply has started

User responseCorrect the problem that is specified by the reasoncode, and reissue the START DATABASE command.


Related informationDSNI006Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID function-id TYPE object-type NAME object-nameDSNI022Icsect-name LPL OR GRECP RECOVERY LOGAPPLY FOR function-name - ID = function-id ATLOGPOINT current-position TO LOGPOINT end-position AT LOGPOINT IN LOCAL TIMESTAMP =at-logpoint-timestamp TO LOGPOINT IN LOCALTIMESTAMP = to-logpoint-timestampDSNI051Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID = function-id TYPE object-type NAME object-nameResource typesType codes are associated with particular typesof resources.

DSNI006I csect-name ASYNCHRONOUSGRECP OR LPL RECOVERY INPROGRESS FOR function-name -ID function-id TYPE object-typeNAME object-name

ExplanationRecovery has started for an object with group bufferpool recovery pending (GRECP) or logical page list(LPL) status.


function-nameThe command or function that triggered therecovery. Expected values are:





System actionThe object is started and GRECP or LPL recovery isinitiated. During LPL or GRECP recovery process,additional messages might be issued, including.

• DSNI005I, which indicates an error• DSNI021I, which indicates successful completion• DSNI051I, which indicates that second pass log

apply has started


You can issue a DISPLAY DATABASE command withthe RESTRICT option for the specified table space orindex space to determine whether the GRECP or LPLexception state has been cleared.

Related reference-DISPLAY DATABASE (Db2) (Db2 Commands)Related informationDSNI005Icsect-name LPL OR GRECP RECOVERY CANNOTBE DONE FOR function-name - ID = function-idOBJECT TYPE object-type OBJECT NAME object-name REASON reason-code TYPE resource-typeNAME resource-nameDSNI021Icsect-name GRECP OR LPL RECOVERY FORfunction-name - ID = function-id TYPE object-type NAME object-name HAS COMPLETEDSUCCESSFULLY.DSNI051Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID = function-id TYPE object-type NAME object-name

DSNI007I csect-name UNABLE TO START/RECOVER BECAUSE UNABLE TODIRECT READ A LOG RECORDLOGRBA logrba

ExplanationUnable to START (or RECOVER) because the necessarylog records could not be accessed. Either an erroroccurred while attempting to allocate or open the logdata set or an expected log record was not found onthe log.

If the message is in response to a START command,issue the -DISPLAY command to determine whichresource(s) was not started. If the message is inresponse to a RECOVER utility, the resource is the

Chapter 7. DSNI messages 229


table space or index space that is the object of theRECOVER.

LOGRBA gives the log RBA of the log record that isunavailable.

System actionThe resource is not started (or recovered) and remainsin the current state. If this is a START command, theresources are processed normally if there are otherdatabases or spaces to be started and they do notinvolve reading the log.

System programmer responseRun the print log map (DSNJU004) utility. This may berun with Db2 up or down. Find the data set thatcontains the requested RBA in the output ofDSNJU004. If the required RBA is not in a listed dataset, one of the following may have occurred:

• The data set was deleted from the bootstrap data setby a run of the change log inventory (DSNJU003)utility. In this case, rerun the utility to insert themissing data set name. Db2 must be down to run thisutility.

• The bootstrap data set has been damaged. In thiscase, the BSDS must be restored from the dump thatoccurred with the most recent archive log data set.DSNJU003 must be run to supply changes thatoccurred during and after the last offload operation.Changes may be determined from the operator'sconsole listing.

If a listed log data set contains the required RBA, thismessage will be preceded by one or more errormessages from the log manager (DSNJ). See thesemessages for appropriate action.

User responseResubmit the utility, or reissue the START command,when the problem with the log has been resolved.

Problem determinationIssue the -DISPLAY command to verify what gotstarted.

DSNI008I DATABASE VALIDATIONPROCEDURE name COULD NOT BELOADED

ExplanationThe database validation procedure identified by 'name'could not be loaded.

User responseCorrect the name, and rerun the application.

DSNI009I csect-name DATABASE EDITPROCEDURE name COULD NOT BELOADED

ExplanationThe database edit procedure identified by 'name'could not be loaded.

User responseCorrect the name, and rerun the application.

DSNI010I BROKEN PAGE ACCESSED TYPEresource-type NAME resource-name MODNAME csect-nameCONN-ID conn-id CORR-ID corr-idLUW-ID luw-id

ExplanationThe page identified by TYPE and NAME could not beaccessed by csect-name, because it is marked aslogically broken.

CONN-ID, CORR-ID, and LUW-ID



conn-id, corr-id, and luw-idIdentifiers for the thread that is involved in theproblem. If luw-id is *, the thread originated at thissite. Correlation IDs beginning with '0nn', where nnis a number from 01 - 28, identify system agents.

User responseIf the TYPE is '00000300', use NAME to determine ifthe page is in an index space or a table space. Use theRECOVER or REPAIR utility to fix the damaged page.For information about RECOVER, see Recovering apage (Db2 Utilities). For information about REPAIR,see Repairing a damaged page (Db2 Utilities). If yoususpect an error in Db2, you might need to report theproblem. For information about identifying andreporting the problem, see Collecting diagnostic data(Collecting data).

DSNI011I PAGE TEMPORARILYUNAVAILABLE TYPE resource-type


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_recoverpage.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_recoverpage.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_repairdamagedpage.html



NAME resource-name MODNAMEmodname ERQUAL erqual

ExplanationThe identified page has been temporarily marked aslogically broken to prevent access until it can berecovered.


modnameThe module named that called a page checkingroutine, which discovered an error in the page.

erqualThe trace identifier for the error in the page.


System actionAutomatic recovery for the page has been scheduled.The current agent will abend with reason code'00C90105', and a dump will be taken. The page willbe unavailable to this and other agents until the onlinerecovery has completed successfully. MessageDSNI010I will be issued, and a 'resource unavailable'condition will be returned to any agents that attemptto access the page. If the online recovery fails, thepage will be marked as broken until it is repaired orrecovered (see message DSNI012I).

User responseSave the dump. Watch for message DSNB215I(indicating successful recovery of the page), orDSNI012I (indicating failure of recovery of the page).

Related information00C90105 (Db2 Codes)DSNI010IBROKEN PAGE ACCESSED TYPE resource-typeNAME resource-name MODNAME csect-nameCONN-ID conn-id CORR-ID corr-id LUW-ID luw-idDSNI012IPAGE LOGICALLY BROKEN TYPE resource-typeNAME resource-name MODNAME modnameERQUAL erqualDSNB215I

csect-name-ONLINE RECOVERY FOR ANINCONSISTENT PAGE HAS BEEN COMPLETEDFOR DBNAME = database-name, SPACENAME =space-name, INSTANCE instance-number, PAGENUMBER = X'page-number'

DSNI012I PAGE LOGICALLY BROKEN TYPEresource-type NAME resource-name MODNAME modnameERQUAL erqual

ExplanationThe identified page is logically incorrect. Additionalattempts to access the page will be denied.


modnameThe name of the log apply module that discoveredan error in the page.

erqualThe trace identifier for the error in the page.X'0000' indicates that an abend occurred duringonline recovery or RECOVER utility. The page ismarked as broken, and recovery fails.


System actionThe page is marked as logically broken, a 04E abendwith reason code 00C90102 is issued, and a dump istaken. The page will be unavailable to this and otheragents until it is repaired.


System programmer responseSee the Explanation section of this message.

User responseSave the dump for analysis by IBM Support. Copy thetable space or index space to another data set for lateranalysis by IBM Support. If you suspect an error inDb2, you might need to report the problem. Forinformation about identifying and reporting the







problem, see Collecting diagnostic data (Collectingdata).

Related information00C90102 (Db2 Codes)

DSNI013I csect-name POTENTIALLYINCONSISTENT DATA REASONreason ERQUAL erqual TYPEresource-type NAME resource-name CONN-ID conn-id CORR-IDcorr-id LUW-ID luw-id

ExplanationThis message identifies a page with potentiallyinconsistent data. This message is issued for eachpage involved in the current data manager operation.



erqualIdentifies the specific abend in the CSECT thatcaused this message to be issued. This informationand the reason code are used by IBM SoftwareSupport to identify the cause of the problem.

conn-idThe connection identifier of the agent that isinvolved in the problem.

corr-idThe correlation identifier of the agent that isinvolved in the problem. Correlation IDs 01 - 028,identify system agents.

luw-idThe logical unit of work identifier of the agent thatis involved in the problem. If the thread originatedat this site, the value of luw-id is *.

For further information, see the Explanation section forthe abend reason code specified in this message.

System actionThe job is abended shortly after this message appears.

Operator responseCollect the console output from the system on whichthe job was run. Save this output for use in problemdetermination.

System programmer responseSee the Problem Determination section for the specificabend reason code.


Problem determinationSee the System Programmer Response section of theabend reason code specified in this message.

DSNI014I csect-name DATA IN USE DURINGABEND REASON 00C90101ERQUAL error-qualifier TYPEresource-type NAME resource-name CONN-ID connection-idCORR-ID correlation-id LUW-IDluw-id

ExplanationThis message identifies a page that was in use at thetime an abend condition occurred with reason code00C90101. A separate instance of this message isissued for each page involved in the current operation.


error-qualifierThe abend in the control section that caused thismessage to be issued.


connection-idThe connection identifier of the agent that isinvolved in the problem.

correlation-idThe correlation identifier of the agent that isinvolved in the problem. Correlation IDs that beginwith 001 through 028, inclusive, identify systemagents.

luw-idThe logical unit of work identifier of the agent thatis involved in the problem. If the thread originatedat this site, the value of luw-id is a *.

System actionThe job abends with reason code 00C90101 after thismessage appears.





Operator responseCollect the console output from the system on whichthe job was run for the period of time spanning thefailure. Save this output for use in problemdetermination.

System programmer responseSee abend reason code 00C90101 for moreinformation.


Problem determinationIn general, the data in these pages is valid. However, ifproblems are reported that repeatedly involve thesame pages or if the same pages are reported by otherabends, analyze the set of pages involved.



DSNI015I OBJECT name IS ALREADYSTARTED FOR RW ACCESS. THEOBJECT WILL REMAIN STARTEDFOR RW ACCESS

ExplanationThe -START DATABASE command with theACCESS(FORCE) keyword was entered, but the objectspecified was already started for read/write access.

DSNI016I RESOURCE TYPE resource-typeNAME resource-name MUST FIRSTBE STOPPED BEFORE IT CAN BESTARTED IN A DIFFERENTACCESS MODE

ExplanationWhen issuing the -START DATABASE command on theROSHARE OWNER system, the object to be startedmust first be stopped before changing access modes.For example, if a table space in a database defined asROSHARE OWNER is started for RW access, before itcan be started for RO access it must be stopped via the-STOP DATABASE command. It can then be started forRO access via the -START DATABASE command.


System actionThe -START DATABASE command is not allowed toproceed.

User responseIssue a -STOP DATABASE command to stop the objectbefore attempting to start it.

Severity8 (error)

DSNI017I RESOURCE TYPE resource-typeNAME resource-name ISINCONSISTENT DUE TO ONE ORMORE PENDING STATES

ExplanationThere are two possible reasons for this message:

1. The header page of a table space, index, orpartition belonging to a database defined asROSHARE OWNER could not be marked asconsistent during the processing of the STOPDATABASE command because one or more of thefollowing was true:

• The table space, index, or partition is in recoverypending status.

• The table space, index, or partition is in checkpending status.

• The table space, index, or partition has pages inthe logical page list (LPL).

• The table space, index, or partition status has autility in progress (UTUT status on the outputfrom a DISPLAY DATABASE command).

• The table space, index, or partition has a utility inprogress that allows read-only access (UTRO onthe output from a DISPLAY DATABASEcommand).

• An I/O error range exists.2. A retained lock is held on the table space, index, or

partition. The retained lock could be signifying apending status.

If the STOP DATABASE command was issued withoutspecifying the SPACENAM parameter, then one ormore of the conditions stated above is true for one or





more table spaces, indexes, or partitions in thespecified database.resource-type and resource-name

The type and name of the resource that themessage identifies. For an explanation of resource-type and resource-name values, see Appendix C,“Resource types,” on page 1207.

System actionFor case 1, if the STOP DATABASE command wasspecified with the SPACENAM parameter, the tablespace, index, or partition is stopped. Db2 does notallow access to an inconsistent table space, index, orpartition by any ROSHARE READ system.

For case 2, no access to an inconsistent table space,index, or partition is allowed until the retained lock isreleased by the failed system at completion of itsrestart.

User responseIssue a DISPLAY DATABASE command to display thestatus of the object in question. Resolve the pendingstates and then reissue the STOP DATABASE commandto ensure that the consistency indicator is reset.

Severity4 (warning)

DSNI018I UNABLE TO GET LOCK FORRESOURCE TYPE resource-typeNAME resource-name. WILL RETRYTO GET LOCK.

ExplanationThe identified resource could not be locked because oflock contention. The lock request is made again forthis resource.


System actionThe lock request is made again for the specifiedresource.


Related conceptsLock contention, suspension, deadlock, andtimeout (Db2 Performance)Objects that are subject to locks (Db2Performance)

DSNI019I THE STOP COMMAND FOR OBJECTname WAS OVERRIDDEN BY ASTART FORCE. THE STOPCOMMAND IS IGNORED.

ExplanationThe object identified by 'name' was not stoppedbecause a START FORCE command on this object wassubsequently issued and processed.

This message is informational only.

System actionThe object is not stopped.


DSNI020I csect-name UNABLE TO DRAINRESOURCE TYPE resource-typeNAME resource-name. WILL RETRYDRAINING THE RESOURCE.

ExplanationThe identified resource could not be drained. The drainrequest is made again for this resource.



System actionThe drain request is made again for the specifiedresource.

Related conceptsClaims and drains (Db2 Performance)

DSNI021I csect-name GRECP OR LPLRECOVERY FOR function-name - ID= function-id TYPE object-typeNAME object-name HASCOMPLETED SUCCESSFULLY.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_lockcontention.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_lockcontention.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_objectoflock.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_objectoflock.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_claimsdrans4concurrency.html

ExplanationRecovery has completed successfully.


function-nameThe function that triggered the recovery: Expectedvalues are:





This message is always preceded by messageDSNI006I, which indicates the beginning of the LPL orGRECP recovery for the object. In addition, thismessage might be preceded by message DSNI051I,which indicates the beginning of second pass LPL orGRECP recovery for the object.

System actionThe object is started normally. The group buffer poolrecovery pending (GRECP) or logical page list (LPL)exception state is cleared.


Related informationDSNI006Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID function-id TYPE object-type NAME object-nameDSNI051Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID = function-id TYPE object-type NAME object-name

DSNI022I csect-name LPL OR GRECPRECOVERY LOG APPLY FORfunction-name - ID = function-id ATLOGPOINT current-position TO

LOGPOINT end-position ATLOGPOINT IN LOCAL TIMESTAMP= at-logpoint-timestamp TOLOGPOINT IN LOCAL TIMESTAMP= to-logpoint-timestamp

ExplanationThis message is issued periodically to show theprogress of group buffer pool recovery pending(GRECP) or logical page list (LPL) recovery.





current-positionThe log point of the log record that is beingprocessed when message DSNI022I is issued. Thisvalue is an RBA in a non-data sharing environmentor an LRSN in a data sharing environment.

end-positionThe log point of the last log record that will beapplied in this recovery. This value is an RBA in anon-data sharing environment or an LRSN in a datasharing environment.

at-logpoint-timestampThe local timestamp of the log point of the logrecord that is being processed when messageDSNI022I is issued. If the log point is an RBA, thestring ********** is displayed.

to-logpoint-timestampThe local timestamp of the log point of the last logrecord that will be applied in this recovery. If thelog point is an RBA, the string ********** isdisplayed.







January JAN

February FEB

March MAR

April APR

May MAY

June JUN

July JUL

August AUG

September SEP

October OCT

November NOV

December DEC


yyyyThe year.


During the LPL or GRECP recovery process, additionalmessages might be issued, including:

• DSNI005I, which indicates an error• DSNI006I, which indicates the start of recovery• DSNI021I, which indicates successful completion• DSNI051I, which indicates that second pass log

apply has started


Related informationDSNI005Icsect-name LPL OR GRECP RECOVERY CANNOTBE DONE FOR function-name - ID = function-idOBJECT TYPE object-type OBJECT NAME object-name REASON reason-code TYPE resource-typeNAME resource-nameDSNI006Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID function-id TYPE object-type NAME object-name

DSNI021Icsect-name GRECP OR LPL RECOVERY FORfunction-name - ID = function-id TYPE object-type NAME object-name HAS COMPLETEDSUCCESSFULLY.DSNI051Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID = function-id TYPE object-type NAME object-name

DSNI023I csect-name PAGE SETdbnam.psnam PART part IS statusON BEHALF OF UR urid. BACKOUTTO logpoint IS REQUIRED.

ExplanationThe value of status is either RESTP (Restart Pending)or AREST (Advisory Restart Pending). This messageindicates that the named UR has backout workpending against the named page set or partition. Thebackout work for this UR against this page set orpartition will be complete after backward processingof the log reaches the identified logpoint. The value forlogpoint will be 'RBA rba' for non-datasharing and'LRSN lrsn' for datasharing environments.

For non-partitioned page sets, the partition given inthe message is the string n/a.

DSNI024I csect-name BACKOUTPROCESSING IS COMPLETE FORPAGE SET dbnam.psnam PARTpart.

ExplanationThis message indicates that backout processing iscomplete for the named table space, index space, orpartition. If the object was in restrictive restartpending state, that state is lifted. If the object was inan advisory restart pending state, locks held on theobject on behalf of postponed abort URs by the Db2member issuing the message are released. Theadvisory restart pending state is lifted if the Db2member issuing the message is the only member stillcontributing to the state.

For non-partitioned page sets, the partition given inthe message is the string "n/a".

DSNI025I csect-name THE FAST LOG APPLYPROCESS REQUIRES aaaaaaaaBYTES OF STORAGE, BUT GOTONLY bbbbbbbb BYTES


ExplanationThe Fast Log Apply process could not obtain all therequired storage. However, the storage acquired isenough for the Fast Log Apply process to continue.

System actionThe Fast Log Apply process continues with the smalleramount of storage for the log buffers.


DSNI026I csect-name THE FAST LOG APPLYPROCESS IS DISABLED BECAUSEALL OF THE ALLOWABLE STORAGEIS EXHAUSTED

ExplanationThere is no ssnmDBM1 storage available for the FastLog Apply process to use. There are too many jobs(RECOVER or -START DB command) running in parallel.

System actionThe recovery of the requested objects continueswithout the Fast Log Apply process.


DSNI027I csect-name THE FAST LOG APPLYPROCESS IS DISABLED BECAUSEIT IS UNABLE TO ACQUIRE THEMINIMUM REQUIRED STORAGE

ExplanationThere is not enough ssnmDBM1 storage available orreserved for the Fast Log Apply process to use.

System actionThe recovery of the requested objects continueswithout the Fast Log Apply process.


DSNI028I csect-name THE NUMBER OFQUALIFIED LOG RECORDS READDURING THE FAST LOG APPLYPROCESS IS log-records AND THENUMBER OF FAST LOG APPLY

BUFFERS PROCESSED ARE fla-buffers

ExplanationThis informational message is issued during the FastLog Apply process. log-records indicates the number oflog records that have been applied during the Fast LogApply process. fla-buffers indicates the number ofbuffers used by the Fast Log Apply process.


DSNI029I csect-name THE FAST LOG APPLYPROCESS IS ACTIVE AND THEAVAILABLE ssnmDBM1 STORAGEIS bytes BYTES

ExplanationThis informational message is issued during the FastLog Apply process for member ssnm. There issufficient storage for the Fast Log Apply process tocontinue, and the remaining amount of availablestorage is displayed in hexadecimal as bytes.


DSNI030I csect-name BACKOUTPROCESSING IS CONTINUINGBEYOND THE REQUESTED LIMITDUE TO CATALOG OR DIRECTORYACTIVITY OF UR urid.

ExplanationThe number of log records requested to be processedduring restart's backward phase have been processed.Under other circumstances further backout processingwould be postponed. However, because the indicatedUR has catalog or directory updates that are notbacked out yet (and because backout against catalogor directory page sets cannot be postponed), backoutprocessing is continuing. It will continue until this UR'sbackout is complete.

System actionBackout processing continues.

DSNI031I csect-name - LOCK ESCALATIONHAS OCCURRED FOR RESOURCENAME = resource-name, LOCKSTATE = lock-state, PLAN NAME :PACKAGE NAME = plan-


name:package-name,COLLECTION-ID = collection-id,STATEMENT NUMBER = statement-number, CORRELATION-ID =correlation-id, CONNECTION-ID =connection-id, LUW-ID = luw-id,THREAD-INFO = thread-information, PARTITION-INFO =partition-info

ExplanationLock escalation has occurred for the specified object.


resource-nameThe name of the escalated resource. The format ofresource-name depends on the type of tablespace:Simple or partitioned table spaces

database-name.tablespace-nameSegmented table space

Either creator-name.table-name or DBID.OBIDof the table

lock-stateThe lock state of the escalated resource, afterescalation.

plan-nameThe name of the executing plan that is associatedwith this thread.

package-nameThe name of the executing package that isassociated with this thread, if one exists.

collection-idThe collection identifier of the package resource, ifone exists.

statement-numberThe statement number of the executing SQLstatement that is associated with this plan.

correlation-idThe correlation identifier of the thread that isassociated with the escalated resource.

connection-idThe connection identifier of the thread that isassociated with the escalated resource.

luw-idThe logical unit of work identifier of the thread thatis associated with the escalated resource.

thread-informationInformation about the thread. The information ispresented in a colon-delimited list that containsthe following segments:

• The primary authorization ID that is associatedwith the thread.

• The name of the user's workstation.• The ID of the user.• The name of the application.• The statement type for the previously executed

statement: dynamic or static.• The statement identifier for the previously

executed statement, if available. The statementidentifier can be used to identify the particularSQL statement. For static statements, thestatement identifier correlates to the STMT_IDcolumn in the SYSIBM.SYSPACKSTMT table. Fordynamic statements, the statement identifiercorrelates to the STMT_ID column in theDSN_STATEMENT_CACHE_TABLE table. Thatstatement might not have contributed to thecurrent failure.

• The name of the role that is associated with thethread.

• The correlation token that can be used tocorrelate work at the remote system with workperformed at the Db2 subsystem. The correlationtoken, if available, is enclosed in '<' and '>'characters, and contains three components,separated by periods:

– A 3 to 39 character IP address.– A 1 to 8 character port address.– A 12 character unique identifier.

An asterisk (*) in any segment indicates that theinformation is not available.

partition-infoThe table space partitions for which lockescalation occurred.



Related conceptsLock escalation (Db2 Performance)

DSNI032I csect-name CANCEL THREADNOBACKOUT COMMAND FAILEDFOR THE THREAD = token REASON= reason


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_lockescalation.html

ExplanationDb2 displays this message when it cannot grant arequest to cancel a thread without backing out datachanges. The reason code explains why the requestwas rejected.token

Identifies a thread whose processing yourequested to cancel. The token is a 1- to 15-digitdecimal number.

reasonIndicates the reason why the command failed.

System actionProcessing terminates normally.

User responseThe reason code specifies the action to be taken.

DSNI033I csect-name PAGE SETdbname.psname PART part-number IS MARKED REFP ANDstatus ON BEHALF OF UR ur-id.RECOVERY TO logout ISREQUIRED.

ExplanationNo further backout processing will be attempted onthe specified page set or partition because backout forthe specified unit of recovery was canceled. Thespecified page set or partition is placed in refresh-pending (REFP) status.


dbname.psnameThe database and page set.

part-numberThe value that identifies the partition or data set.

statusAdditional status set on the specified object.

ur-idThe unit of recovery.

logoutRBA or LRSN value.

User responseIf the object in refresh-pending status is a table space,you can resolve the REFP,LPL state of the specifiedpage set or partition in one of the following ways:

• Run the RECOVER utility to perform a point-in-timerecovery.

• Run the LOAD utility with the REPLACE option toresolve the REFP,LPL state.

If the page set is an index space, run the REBUILDINDEX utility to perform a point-in-time recovery andresolve the REFP,RBDP or REFP,LPL status. You canuse the RBA or LRSN value in this message for point-in-time recovery.

The DSNI033I message might be issued multipletimes for a page set. (The message is issued once perunit of recovery.) If you run the RECOVER utility withpoint-in-time recovery to resolve the exception states,use the highest of the logout points.


Related referenceAdvisory or restrictive states (Db2 Utilities)RECOVER (Db2 Utilities)REBUILD INDEX (Db2 Utilities)

DSNI034I csect-name TABLE SPACE table-space-name IS IN AUX WARNINGSTATE

ExplanationDb2 attempted to recover table space table-space-name, but no log records exist because the table spacewas created with the LOG NO option. The table spaceis placed in an auxiliary warning state. You can use SQLstatements to update the LOB values that are in erroror to delete the row that contains the LOB values. Inaddition, you can use SQL statements to access validLOBs. However, you cannot use SQL statements toretrieve a LOB value that is not valid.

System actionDb2 marks the LOB values that are in error as not valid.Processing continues.

Programmer responseUse SQL statements to update or delete the LOBvalues in error. Use the CHECK LOB utility to verify thatall errors were corrected and to reset the auxiliarywarning state. The auxiliary warning state can also bereset using the REPAIR utility with SET NOAUXWARN.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_advisoryrestrictivestates.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_rebuildindex.html

DSNI036I csect-name THE REAL-TIMESTATISTICS COLLECTIONPROCESS IS DISABLED

ExplanationAn error prevents Db2 from externalizing the in-memory statistics. The error is generally a persistenterror and must be remedied before the process can beenabled. Look for prior messages to identify the natureof the problem.

System actionThe statistics database is implicitly stopped and nofurther attempt will be made to externalize the in-memory statistics.


System programmer responseInspect the console for prior messages and refer tothose messages for problem determination.

DSNI037I csect-name THE REAL-TIMESTATISTICS COLLECTIONPROCESS COULD NOT ACCESS ANOBJECT IN THE REAL-TIMESTATISTICS DATABASE

ExplanationAn error prevents Db2 from externalizing the in-memory statistics. An attempt failed to insert, update,or delete a row in the statistics database. The error isgenerally transient (lock timeout or resourceunavailable). If the operation is retried, it is likely tosucceed.

System actionThe statistics are kept in-memory until the nextopportunity to externalize them.

DSNI038I csect-name THE REAL-TIMESTATISTICS COLLECTIONPROCESS IS ENABLED

ExplanationThe statistics database started successfully. Therequired object descriptors in the statistics databaseexist and have the correct attributes. Db2 proceeds toexternalize in-memory statistics for all modifiedobjects.

System actionThe database is started R/w.


DSNI040I csect-name RESTORE SYSTEMUTILITY PROCESSING LOG RANGEFROM rba/lrsn xxxxxx TO yyyyyy

ExplanationThis message periodically shows the progress ofsystem level recovery made by the RESTORE SYSTEMutility. In non-data sharing, the log range is RBA. Indata sharing, the log range represents LRSN value. Thevalue for xxxxxxxx is the RBA or LRSN value of thecurrent log record being processed and the yyyyyyyyvalue is the RBA or LRSN of the last log record to beprocessed by the RESTORE SYSTEM utility.

System actionSystem Level Point-In-Time recovery continues.


DSNI041I csect-name STARTACCESS(FORCE) CANNOT BEISSUED AGAINST TARGET obj-typeobj-qual.obj-name part DUE TOSTOPPED UTILITIES ON VERSIONversion-number. REQUEST ISREJECTED.

ExplanationThe object cannot be started due to outstandingutilities on a different version. The status of the objectis unchanged.

version-number is the version on which the utility wasrunning.

obj-type is table space or index space.

obj-qual is the database name.

obj_name is the table space or index space name.

part represents the partition number for a partitionedtable space.



User responseUse the DISPLAY UTILITY command to see whatutilities are outstanding. Issue the -START DATABASEACCESS(FORCE) command on the same version as theversion on which the stopped utility was running. Ifthere is more than one utility outstanding on the objectand the utilities were submitted on a different releaseof Db2, start the correct version of Db2 and use the -TERM UTILITY command to terminate each utility.

DSNI042I csect-name - PAGE SET HEADERRBA function-name- ID function-idDB ID database-id. PS ID pageset-id PART # partition-number RBAheader-page RBA

ExplanationThis informational message displays the header pageRBA that is used to determine the LPL or GRECPrecovery range for the specified page set. It isdisplayed one time for each LPL recovery, for eachpage set and each data sharing group.



function-nameThe name of the function, such as a STARTDATABASE command, that was issued.

function-idA decimal number that represents the function.

database-idThe ID of the database where the page set exists.

pageset-idThe ID of the page set where the pages exist.

partition-numberThe number of the partition where the pages exist.

header-pageThe RBA value that is on the header page of thepage set.

System actionThe recovery continues.

User responseWait for message DSNI021I, which indicates the endof recovery, or for message DSNI005I, which indicatesan error occurred during recovery.

Related informationDSNI005Icsect-name LPL OR GRECP RECOVERY CANNOTBE DONE FOR function-name - ID = function-idOBJECT TYPE object-type OBJECT NAME object-name REASON reason-code TYPE resource-typeNAME resource-nameDSNI021Icsect-name GRECP OR LPL RECOVERY FORfunction-name - ID = function-id TYPE object-type NAME object-name HAS COMPLETEDSUCCESSFULLY.

DSNI043I csect-name - MERGED LOG APPLYRANGE function-name-ID function-id MEMBER ID member-id FROMtype sequence-start TO typesequence-end

ExplanationThis informational message displays the broad LRSNor RBA range, merged from all members of the datasharing group. The range is used to determine the LPLor GRECP recovery range for the specified page set. Itis displayed on time for each LPL recovery, for eachmember.





member-idThe numeric identifier for the data sharingmember.

typeAn indicator of the log record sequence numberreferenced in the message:LRSN

The log record sequence number is used in adata sharing environment.

RBAThe relative byte address is used in a non-datasharing environment.

sequence-startIndicator of the beginning of the sequenceidentified by type.


sequence-endIndicator of the end of the sequence identified bytype.



Related informationDSNI005Icsect-name LPL OR GRECP RECOVERY CANNOTBE DONE FOR function-name - ID = function-idOBJECT TYPE object-type OBJECT NAME object-name REASON reason-code TYPE resource-typeNAME resource-nameDSNI021Icsect-name GRECP OR LPL RECOVERY FORfunction-name - ID = function-id TYPE object-type NAME object-name HAS COMPLETEDSUCCESSFULLY.

DSNI044I csect-name- PAGE LOG APPLYRANGE function-name -IDfunction-id DB ID database-id PSID pageset-id PART # partition-number MEMBER ID member-idFROM PAGE # from-page TO PAGE# to-page FROM type sequence-start TO type sequence-end

ExplanationThis informational message displays the LRSN or RBArange that is used to determine LPL or GRECP recoveryrange for the specified page set in the data sharinggroup member.





database-idThe ID of the database where the page set exists.

pageset-idThe ID of the page set where the pages exist.

partition-numberThe number of the partition where the pages exist.

member-idThe numeric identifier for the data sharingmember.

from-pageThe beginning page number for the range wherethe log is to be applied.

to-pageThe ending page number for the range where thelog is to be applied.

typeAn indicator of the log record sequence numberreferenced in the message:LRSN

The log record sequence number is used in adata sharing environment.

RBAThe relative byte address is used in a non-datasharing environment.

sequence-startAn indicator of the beginning of the sequenceidentified by type.

sequence-endAn indicator of the end of the sequence identifiedby type.



Related informationDSNI005Icsect-name LPL OR GRECP RECOVERY CANNOTBE DONE FOR function-name - ID = function-idOBJECT TYPE object-type OBJECT NAME object-name REASON reason-code TYPE resource-typeNAME resource-nameDSNI021Icsect-name GRECP OR LPL RECOVERY FORfunction-name - ID = function-id TYPE object-


type NAME object-name HAS COMPLETEDSUCCESSFULLY.

DSNI045I OPEN FAILED FOR DATABASE db-name SPACE NAME ps-name PARTpart-num REASON reason-code

ExplanationThe local member failed to physically or logically openthe indicated object.

db-nameThe database name for the page set that failed toopen.

ps-nameThe name of page set that failed to open.

part-numThe partition that failed to open. part-num is 0 fornon-partitioned page sets.

reason-codeThe reason code for the failure.


Operator response1. Ensure that the buffer pool is activated.2. Use the reason-code to determine the cause of the

failure.3. Correct the error and re-issue the command.

DSNI046I csect-name OBJECT IN ERRORREASON reason-code ERQUALerror-qualifier NAME object-nameDBID database-id OBID object-idLRSN log-record>

ExplanationAn error occurred during processing of a table space,table space partition, index space, index partition, orlogical index partition. One of the following conditionsoccurred:

• An error occurred when Db2 processed a DBETexception state for a table space, index space, orpartition of a partitioned object.

• An error occurred when Db2 was unable to access apage set in backward log recovery phase duringrestart.


reason-codeThe Db2 reason code that is listed in the dump thataccompanies this message.

error-qualifierThe abend in the control section that caused thismessage to be issued.

object-nameThe name of the table space or index space thatencountered the problem. A partition number isincluded where applicable.

database-idThe database identifier (DBID).

object-idThe object identifier (OBID).

log-recordThe LRSN or RBA of the log record that was beingprocessed when the error occurred. If no logrecord was being processed, this value is blank.

System actionThe system action depends on the situation in whichthe error occurred:

Accessing a page in backward log recovery phaseDb2 places the table space or index space in RECPand DBETE status. It then abends and generates adump. Db2 tolerates the page set access error sothat it can restart.

Processing a DBET exception stateDb2 places the table space or index space in RECP,RBDP, or PSRBD status and DBETE status. It thenabends and generates a dump. Db2 tolerates theexception state error so that it can restart or theRESTORE SYSTEM utility can continue.

User responseIssue the appropriate DISPLAY command to see thestatus of the object. Use one of the following methodsto reset the DBETE and RECP, RBDP, or PSRBDstatuses:

• Use the RECOVER utility or the LOAD utility with theREPLACE option to recover a table space or indexspace.

• Use the REBUILD INDEX utility to rebuild an indexspace.

• Use the START DATABASE command with thefollowing options:

START DATABASE(database-name) SP(space-name) ACCESS(FORCE)

Contact IBM Software Support to report the problem.Db2 log records need to be analyzed in order to


diagnose the cause of the problem, and determine ifthe exception state error needs to be handled.

Related conceptsDb2 reason codes (Db2 Codes)Related reference-START DATABASE (Db2) (Db2 Commands)LOAD (Db2 Utilities)REBUILD INDEX (Db2 Utilities)RECOVER (Db2 Utilities)

DSNI047I csect-name UNABLE TO ACCESSOBJECT TYPE object-type OBJECTNAME object-name REASONreason-code TYPE resource-typeNAME resource-name

ExplanationThe resource identified could not be accessed becauseit was unavailable. The resource could be a database, atable space, an index space, or a partition within atable space or index space.


object-type and object-nameThe type and name of the object. If the Db2catalog is unavailable,object-type contains binaryzeros and object-name contains blanks.

reason-codeThe reason code for the unavailable resource.


System actionThe specified database, space, or partition is notaccessed, and remains in its current state. If there areother databases, spaces, or partitions to be accessed,they are processed normally.

User responseCorrect the resource unavailable problem and reissuethe -ACCESS DATABASE command.

Related informationResource typesType codes are associated with particular typesof resources.

DSNI048I GROUP BUFFERPOOLDEPENDENCY CANNOT BEREMOVED FOR DATABASE db-name SPACE NAME ps-name PARTpart-num REASON reason-text

ExplanationDb2 failed to remove group buffer pool dependency forthe indicated object.

db-nameThe database name for the page set that failed tobe removed from group buffer pool dependency.

ps-nameThe name of page set that failed to be removedfrom group buffer pool dependency.

part-numThe partition that failed to be removed from groupbuffer pool dependency. part-num is 0 for non-partitioned page sets.

reason-textText that indicates one of the following reasons forthe failure:

• DRAIN LOCK FAILURE• RETAINED LOCKS EXIST• REMOTE CLAIMERS EXIST• LOCAL CLAIMERS EXIST• CASTOUT PROBLEM


Operator responseDetermine the cause of the failure from the reason-textby using the DISPLAY DATABSE command with theLOCKS or CLAIMERS keyword. Reissue the ACCESS DBMODE(NGBPDEP) command after the indicated objectis free.

Related reference-DISPLAY DATABASE (Db2) (Db2 Commands)-ACCESS DATABASE (Db2) (Db2 Commands)

DSNI049I csect-name GRECP OR LPLRECOVERY FOR function-name - ID= function-id HAS COMPLETED.

ExplanationThe group buffer pool recovery pending (GRECP) orlogical page list (LPL) exception state of table spacesor index spaces in a recovery function has beencompleted.





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_rebuildindex.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_accessdatabase.html




function-idA decimal number that represents a recoveryfunction. This number corresponds to the functionID number in DSNI006I, DSNI021I, and DSNI051Imessages.

Messages DSNI006I (beginning of recovery),DSNI051I (beginning of second pass recovery), andDSNI021I (end of recovery) report about recovering asingle table space or index space within a recoveryfunction. A recovery function can recover multipleobjects.

Message DSNI049I indicates the end of a recoveryfunction.

System actionThe recovery function that is identified by function-name completes normally.

Operator responseNo action is required.

Related reference-START DATABASE (Db2) (Db2 Commands)Related informationDSNI006Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID function-id TYPE object-type NAME object-nameDSNI021Icsect-name GRECP OR LPL RECOVERY FORfunction-name - ID = function-id TYPE object-type NAME object-name HAS COMPLETEDSUCCESSFULLY.DSNI051Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID = function-id TYPE object-type NAME object-name

DSNI050I PAGE LOGICALLY BROKENDURING FLASH COPY WITHCONSISTENCY TYPE resource-type

NAME resource-name DBID dbidOBID obid PAGE RBA OR LRSNpage-rba-or-lrsn LOG RBA ORLRSN log-rba-or-lrsn MODNAMEmodname ERQUAL erqual

ExplanationThe identified page is logically incorrect. Additionalattempts to access the page will be denied.


dbidThe DBID of the database that was being copied.

obidThe OBID of the table space or index space in thedatabase.

page-rba-or-lrsnThe RBA value in a non-data-sharing environment,or the LRSN value in a data sharing environment, ofthe last page update.

log-rba-or-lrsnThe RBA value in a non-data-sharing environment,or the LRSN value in a data sharing environment, ofthe log record that was being processed when thelogically broken page was discovered.

modnameThe name of the log apply module that discoveredan error in the page.

erqualThe trace identifier for the error in the page.X'0000' indicates that an abend occurred duringonline recovery or the RECOVER utility. The page ismarked as broken, and recovery continues.


System actionThe page is marked as logically broken, a 04E abendwith reason code 00C90102 is issued, and a dump istaken. The page is unavailable to this and other agentsuntil it is repaired.






User responseSave the dump for analysis by IBM Support. Copy thetable space or index space to another data set for lateranalysis by IBM Support. If you suspect an error inDb2, you might need to report the problem. Forinformation about identifying and reporting theproblem, see Collecting diagnostic data (Collectingdata).


DSNI051I csect-name ASYNCHRONOUSGRECP OR LPL RECOVERY INPROGRESS FOR function-name -ID = function-id TYPE object-typeNAME object-name

ExplanationThe second pass log apply has started for an objectwith group buffer pool recovery pending (GRECP) orlogical page list (LPL) status.





object-typeThe type of object, which is an index space.


System actionThe object is started and the second pass log apply forGRECP or LPL recovery is initiated. During the LPL orGRECP recovery process, additional messages mightbe issued, including:

• DSNI005I, which indicates an error• DSNI006I, which indicates the start of recovery• DSNI021I, which indicates successful completion• DSNI022I, which provides the status of recovery

operations


You can issue a DISPLAY DATABASE command withthe RESTRICT option for the specified index space todetermine whether the GRECP or LPL exception statehas been cleared.

Related reference-DISPLAY DATABASE (Db2) (Db2 Commands)Related informationDSNI005Icsect-name LPL OR GRECP RECOVERY CANNOTBE DONE FOR function-name - ID = function-idOBJECT TYPE object-type OBJECT NAME object-name REASON reason-code TYPE resource-typeNAME resource-nameDSNI006Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID function-id TYPE object-type NAME object-nameDSNI021Icsect-name GRECP OR LPL RECOVERY FORfunction-name - ID = function-id TYPE object-type NAME object-name HAS COMPLETEDSUCCESSFULLY.DSNI022Icsect-name LPL OR GRECP RECOVERY LOGAPPLY FOR function-name - ID = function-id ATLOGPOINT current-position TO LOGPOINT end-position AT LOGPOINT IN LOCAL TIMESTAMP =at-logpoint-timestamp TO LOGPOINT IN LOCALTIMESTAMP = to-logpoint-timestamp

DSNI052I csect-name AN AGENT HASEXCEEDED THE THRESHOLD FORSTORAGE USE IN WORK FILEDATABASE database-name FORobject-type.THRESHOLD=percentagePERCENT. TOTAL STORAGECONFIGURED=total-storage KB.CONNECTION ID = connection-id.CORRELATION ID = correlation-id.LUWID=luwid. PACKAGENAME=package-name. PLANNAME=plan-name.

ExplanationThe total amount of storage that an agent used in thework file database exceeded the threshold that isdefined by subsystem parameterWFSTGUSE_AGENT_THRESHOLD.







database-nameThe name of the work file database.

object-typeThe type of object. Possible values are:DECLARED GLOBAL TEMP TABLES

Specifies that the storage is being used fordeclared temporary tables.

WORK FILESSpecifies that the storage is being used forwork files.

DECLARED GLOBAL TEMP TABLES AND WORKFILES

Specifies that the storage is being used fordeclared temporary tables and work files.

percentageThe maximum percentage of work file databasestorage that an agent can use before this messageis issued. This value is the value of subsystemparameter WFSTGUSE_AGENT_THRESHOLD.

total-storageThe total amount of storage that is configured forthe specified object type, in kilobytes.

connection-idThe connection identifier of the agent.

correlation-idThe correlation identifier of the agent.

luwidThe logical unit of work ID of the agent. An asterisk(*) denotes that the thread originated at the localsite.

package-nameThe package name that is associated with theagent.

plan-nameThe plan name that is associated with the agent.

This message is issued once within each commit scopein the application.


System programmer responseWork with the application programmer to determinehow the application program is using space in the workfile database.

Determine whether the threshold that is specified bysubsystem parameterWFSTGUSE_AGENT_THRESHOLD is too low.

If WFSTGUSE_AGENT_THRESHOLD is not too low,evaluate the type of work file activity that the agent isperforming. Take one or both of the following actions:

• Create additional table spaces in the work filedatabase of the object types that are specified in thismessage.

Use the DSNTWFG exec in job step DSNTIST ofinstallation job DSNTIJTM to create additional tablespaces.

• Change the value of subsystem parameter WFDBSEPfrom NO to YES.

Work file table spaces can be used for declaredtemporary tables or for work file work, such assorting. When subsystem parameter WFDBSEP is setto NO, Db2 selects work file table spaces that cangrow into secondary extents for declared temporarytables, and chooses work file table spaces thatcannot grow into secondary extents for work filework. If there is not enough space in one type oftable space, Db2 switches to the other type. WhenDb2 uses work file table spaces that are designatedfor work file activity for declared temporary tables,space for work file activity might be quicklyconsumed. When Db2 uses work file table spacesthat are designated for declared temporary tablesfor work file activity, space for declared temporarytable tables might be rapidly consumed because ofgrowth through secondary extents. To prevent Db2from switching from one type of table space to theother, set WFDBSEP to YES. Doing so can causehigh-consuming agents to experience resourceunavailable conditions, but can help protect otheragents on the system that are using work fileresources.

Programmer responseUse the agent information in the message todetermine which application exceeded space usethreshold WFSTGUSE_AGENT_THRESHOLD. Examinethe application to determine the ways in which theapplication is using space in the work file database.

Related tasksInstallation step 16: Create default storagegroup, define temporary work files, and bindDb2 REXX Language Support: DSNTIJTM (Db2Installation and Migration)Related referenceAGENT LEVEL THRESHOLD field(WFSTGUSE_AGENT_THRESHOLD subsystemparameter) (Db2 Installation and Migration)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntijtm.html




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_wfstguseagentthreshold.html



SEPARATE WORK FILES field (WFDBSEPsubsystem parameter) (Db2 Installation andMigration)

DSNI053I csect-name THE DB2 SUBSYSTEMHAS EXCEEDED THE THRESHOLDFOR STORAGE USE IN WORK FILEDATABASE database-name FORobject-type.THRESHOLD=percentagePERCENT. TOTAL STORAGECONFIGURED=total-storage KB.

ExplanationThis message warns of a possible storage shortage inthe work file database. The amount of storage that isbeing used has exceeded the system-level warningthreshold that is defined by subsystem parameterWFSTGUSE_SYSTEM_THRESHOLD.


database-nameThe name of the work file database.

object-typeThe type of object. Possible values are:DECLARED GLOBAL TEMP TABLES

Specifies that the storage is being used fordeclared temporary tables.

WORK FILESSpecifies that the storage is being used forwork files.

DECLARED GLOBAL TEMP TABLES AND WORKFILES

Specifies that the storage is being used fordeclared temporary tables and work files.

percentageThe maximum percentage of work file databasestorage that is used before this warning is issued.This value is the value of subsystem parameterWFSTGUSE_SYSTEM_THRESHOLD.

total-storageThe total amount of storage that is configured forthe work file database, in kilobytes.

This message is issued at five-minute intervals, for aslong as the criteria for issuing the message are met.


If the situation is not alleviated, applications that usethe work file database might fail.

System programmer responseDetermine whether the warning threshold that isspecified by subsystem parameterWFSTGUSE_SYSTEM_THRESHOLD is too low.

If WFSTGUSE_AGENT_THRESHOLD is not too low, takeone or both of the following actions:

• Create additional table spaces in the work filedatabase of the object types that are specified in thismessage.

Use the DSNTWFG exec in job step DSNTIST ofinstallation job DSNTIJTM to create additional tablespaces.

• Change the value of subsystem parameter WFDBSEPfrom NO to YES.

Work file table spaces can be used for declaredtemporary tables or for work file work, such assorting. When subsystem parameter WFDBSEP is setto NO, Db2 selects work file table spaces that cangrow into secondary extents for declared temporarytables, and chooses work file table spaces thatcannot grow into secondary extents for work filework. If there is not enough space in one type oftable space, Db2 switches to the other type. WhenDb2 uses work file table spaces that are designatedfor work file activity for declared temporary tables,space for work file activity might be quicklyconsumed. When Db2 uses work file table spacesthat are designated for declared temporary tablesfor work file activity, space for declared temporarytable tables might be rapidly consumed because ofgrowth through secondary extents. To prevent Db2from switching from one type of table space to theother, set WFDBSEP to YES. Doing so can causehigh-consuming agents to experience resourceunavailable conditions, but can help protect otheragents on the system that are using work fileresources.

Related tasksInstallation step 16: Create default storagegroup, define temporary work files, and bindDb2 REXX Language Support: DSNTIJTM (Db2Installation and Migration)Related referenceSYSTEM LEVEL THRESHOLD field(WFSTGUSE_SYSTEM_THRESHOLD subsystemparameter) (Db2 Installation and Migration)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_wfdbsep.html







https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_wfstgusesystemthreshold.html



Chapter 8. DSNJ messagesMessage identifiers that begin with DSNJ communicate information about the recovery log manager.

DSNJ001I csect-name CURRENT COPY nACTIVE LOG DATA SET ISDSNAME=..., STARTRBA=...,ENDRBA=...

ExplanationThis message is generated for one of two reasons:

1. When the log manager is initialized, it sends thisinformational message to identify the current activelog data sets (copy-1 and, if dual logging is used,copy-2).

2. When the current active log data set is full, Db2 willswitch to the next available active log data set. Thismessage identifies the next available active logdata set which will be used for logging.

The value specified by the STARTRBA=value keywordis the RBA of the first byte of log data in the nameddata set. The value specified by the ENDRBA=valuekeyword is the RBA of the last possible byte in the dataset. These values may later be needed for aconditional restart.

System programmer responseNone required. However, if recovery is required,information from this message may be required asinput to the change log inventory (DSNJU003) utility.

DSNJ002I FULL ACTIVE LOG DATA SETDSNAME=..., STARTRBA=...,ENDRBA=...

ExplanationThis message is sent at the time the log manager fillsan active log data set and switches to a new emptydata set. The message shows the name and log RBArange of the full data set.

System programmer responseNone required. However, if recovery is requiredinformation from this message may be required asinput to the change log inventory (DSNJU003) utility.

DSNJ003I csect-name FULL ARCHIVE LOGVOLUME DSNAME=...,STARTRBA=..., ENDRBA=...,STARTxxxx=..., ENDxxxx=...,UNIT=..., COPYnVOL=...,VOLSPAN=..., CATLG=...

ExplanationOffloading for the specified archive log data set wassuccessfully completed for the given volume. If thedata set spans multiple tape volumes, this message isgenerated for each tape volume. If the data set spansmultiple DASD volumes, only one message will begenerated displaying the first VOLSER, appended witha plus sign ('+') to indicate the data set spans multiplevolumes. 'xxxx' is replaced by either TIME or LRSN.

System actionAn archive log data set has been created, and thearchive log data set inventory in the bootstrap data set(BSDS) has been updated with the information in themessage:DSNAME

The name of the archive log data set.STARTRBA

The starting RBA contained in the volume.ENDRBA

The ending RBA contained in the volume.STARTLRSN

The starting LRSN contained in the volume for datasharing systems.

ENDLRSNThe ending LRSN contained in the volume for datasharing systems.

STARTTIMEThe starting store-clock value of the log records inthe volume for non-data sharing systems.

ENDTIMEThe ending store-clock value of the log records inthe volume for non-data sharing systems.

UNITThe device unit to which the data set wasallocated.

COPYnVOLThe name of the volume. This message keyword isdisplayed as COPY1VOL if this is the copy-1archive log data set, and as COPY2VOL if this is thecopy-2 archive log data set.

VOLSPANAn indicator to denote one of four conditions:

• If '00', the data set is entirely contained on thevolume specified by 'COPYnVOL'.


• If '01', this is the first entry of a multivolume dataset.

• If '11', this is the middle entry of a multivolumedata set.

• If '10', this is the last entry of a multivolume dataset.

CATLGAn indicator to denote one of two conditions:

• If 'NO', the archive log data set is uncataloged.• If 'YES', the archive log data set is cataloged.

The BSDS is automatically updated with theinformation contained in this message; however, ifrecovery is required, information from this messagemay be required as input to the change log inventoryutility (DSNJU003).

DSNJ004I ACTIVE LOG COPY n INACTIVE,LOG IN SINGLE MODE, ENDRBA=...

ExplanationThis message is sent when the dual active loggingoption is selected and copy 'n' becomes inactive. A logcopy becomes inactive when the next active log dataset is not ready when required. ENDRBA is the lastbyte of log data written on copy 'n'. This is usuallycaused by a delay in off-load.

System actionThe log is switched to single mode until the next dataset for copy 'n' is ready for logging.

If Db2 is shut down or abends while in single modewith the ZPARM option still set for dual active datasets, the previous state of the active log data setsdetermines what happens when Db2 is started, asfollows:

• If fewer than two data sets are available (not flaggedas STOPPED) for each set of active logs, Db2 startupterminates and message DSNJ112E is issued.

• If an active log data set is in NOTREUSABLE state,Db2 can be started in single logging mode, but dualmode takes effect when the other active log data setbecomes available after offloading.


Operator responseExecute an MVS Display System Requests command (DR,L for example) to ensure that there are nooutstanding requests that are related to the log off-load process. Take the necessary action to satisfy anyrequests, and permit off-load to continue.

System programmer responseIf the switch to single mode was caused by the lack ofa resource required for off-load, the necessaryresource should be made available to allow off-load tocomplete and thus permit dual logging to proceed. Ifrecovery is required, information from this messagemight be required as input to the change log inventory(DSNJU003) utility.

DSNJ005I ACTIVE LOG COPY n IS ACTIVE,LOG IN DUAL MODE, STARTRBA=...

ExplanationThis message is sent when copy 'n' of the log becomesactive after previously being flagged as inactive.STARTRBA is the RBA of the first byte of log datawritten on copy 'n' after it was activated.


DSNJ006I ALLOCATION FOR NEW ARCHIVELOG DATA SET HAS BEENCANCELLED BY OPERATOR.

ExplanationThis message is sent if the operator answers 'N' to theWTOR message DSNJ008E.

System actionIf the allocation is for copy 1 archive log data set,offload terminates processing until the next time it isactivated. If copy 1 has already been allocated andthis request is for copy 2, offload switches to singleoffload mode for this data set only.

DSNJ007I csect-name OPERATOR CANCELEDMOUNT OF ARCHIVE VOL SER=volser

ExplanationIf the operator answers 'N' to the WTOR messageDSNJ009I, this message is issued. The variable'volser' is the volume serial of an archive log volumerequired for the read request.

System actionThe read request for the archive log volume fails. If therequest was issued with the COND=YES parameter,return code 12 and reason code 00D1032B are


returned to the requester. Otherwise, Db2 abends withreason code 00D1032B.

DSNJ008E nn OF mm ACTIVE LOGS AREFULL. ssname NEEDS ARCHIVESCRATCH. REPLY Y WHEN DEVICEREADY OR N TO CANCEL.

ExplanationThe installation has requested a WTOR before archivelog data set allocation. Db2 needs a scratch volume foroffloading an active log data set.

ssnameThe name of the Db2 subsystem.

nnThe number of full active log data sets.

mmThe total number of active log data sets.

System actionThe offload task waits for the operator's reply.

Operator responseThe operator has three options:

• Get a scratch volume ready, make sure there is anavailable unit for the volume, and reply 'Y'. Db2 thencontinues with the offload.

• Determine from the number of active log data setsavailable whether the offload can be delayed untilthe next time an active log data set becomes full. Ifthe process can be delayed, then reply 'N'.

This response has two possible effects.

– If dual archive logging is in effect and thisallocation is for a copy 1 archive data set, the 'N'response delays the offload process until the nextactive log data set becomes full.

– However, if the copy 1 archive data set has alreadybeen allocated and this request is for copy 2, the'N' response causes the offload to switch to singlearchive mode (the switch is for this data set only).

• Defer giving a response. This causes offload to waitbefore processing. However, because offload is aseparate service task, the wait does not affect Db2performance.

If offloading to DASD, an error has occurredattempting to allocate an archive log data set. Reply 'Y'to receive the error messages.

DSNJ009E ssname NEEDS VOL SER=nnnnnn.REPLY Y TO CONTINUE OR N TOCANCEL

ExplanationThe installation requested WTOR before archive logdata set allocation. Db2 needs the specified archivevolume for a read operation. The subsystem name is'ssname'.

System actionThe archive log read service task waits for theoperator's reply. This wait affects the agent for whichthe log read was issued and any other agents thatmight be waiting on the log read service task queue.

Operator responseLocate the requested volume, ensure that a device isavailable, and reply 'Y'. Db2 continues with dynamicallocation and then begins reading the log.

If dual archiving is in effect, a response of 'N' causesarchive read to reissue the message for the copy 'Z'copy 2 archive VOLSER with the same RBA range. Aresponse of 'N' to this second WTOR, or to the initialWTOR for single archiving, causes the archive readservice task to fail with unpredictable results.

DSNJ010I csect-name INVALID RESPONSE.WTOR WILL BE REPEATED.

ExplanationA WTOR was issued during archive data set allocation.The user did not respond correctly to the message.Either 'Y' or 'N' must be entered.

System actionThe original WTOR is repeated.

Operator responseReply as indicated in the repeated message.

DSNJ011I CONDITIONAL RESTART RECORDrecord-identifier CREATED ATtimestamp WAS FOUND. REPLY YTO USE, N TO CANCEL

ExplanationWhen the log manager was initialized, a conditionalrestart control record was found in the bootstrap dataset.

This message provides the following information tohelp identify the conditional restart record that will beused:

Chapter 8. DSNJ messages 251

• A record identifier, which is a 4 byte hexadecimalnumber

• The creation timestamp, in the format yy.dddhh:mm:yy

Two-digit indicator for the year.ddd

Three-digit indicator for the day of the year.hh:mm

Indicator for the time of the day.

System actionThe system action depends on the reply.

'Y'Db2 is started conditionally, using the record thatwas found.

'N'Db2 startup terminates.

Operator responseIf a Db2 conditional restart is to be done and if thedate and time displayed are correct, then reply 'Y' tothe outstanding message. If you are not sure, or if youdo not want to use the indicated record, contact thesystem programmer.

System programmer responseIf a normal restart of Db2 has failed and you havecreated a conditional restart control record with thechange log inventory (DSNJU003) utility, checkwhether the time and date in the message agree withwhen you created that record. If they do agree, reply'Y' to the outstanding WTOR. If they do not, reply 'N'and investigate the discrepancy.

Related conceptsRecovering from BSDS or log failures duringrestart (Db2 Administration Guide)Related referenceDSNJU003 (change log inventory) (Db2 Utilities)DSNJU004 (print log map) (Db2 Utilities)

DSNJ012I ERROR ccc READING RBA rrr INDATA SET ddd CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy

ExplanationWhile scanning log records read into a buffer, the logmanager detected a logical error with reason code'ccc'. 'rrr' is the log RBA of the segment in the buffer at

which the error was detected. 'ddd' is the name of theactive or archive log data set from which the recordwas read. If 'ddd' is blank, the data was read from anactive log output buffer.

The connection and correlation IDs identify the user orapplication that encountered the problem. Messagesthat have the same connection ID and correlation IDrelate to the same user. Correlation IDs beginning with'0nn' where 'nn' is a number from 01 to 28, identifysystem agents.

If you suspect an error in Db2, you might need toreport the problem. For information about identifyingand reporting the problem, see Collecting diagnosticdata (Collecting data). for information about recoveryfrom log failures.

System actionThe application program that invoked the log manageris terminated with reason code 'ccc'. However,information in this message may be useful indiagnosing the abend that will follow.

DSNJ013I TERMINAL ERROR ccc IN BUFFERrrr BEFORE ACTIVE LOG WRITE

ExplanationA scan of the log output buffer just prior to writing thebuffer detected an inconsistency in the log data. 'ccc'is the abend reason code associated with the SDUMPthat is produced. 'rrr' is the log RBA at which the errorwas detected.

System actionDb2 will terminate with a dump, and will not write thedamaged buffer to either COPY 1 or COPY 2 active logdata set.

Operator responseNotify the system programmer. Start Db2 after itterminates.

System programmer responseBecause the damaged buffer has not been written to alog data set, Db2 may be restarted. No correctiveaction is required.

Problem determinationIn the Db2 formatted block section of the dump, locatethe chain of LBCE blocks. Those are log buffer controlelements, and each LBCE controls one 4KB log outputbuffer. LBCEBUFF, at offset X'20' in the LBCE, points to


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverbsdsorlogfailureduringrestart.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_dsnju003.html




the buffer, which is always on a 4KB boundary. The logRBA of the first byte of the buffer is in a 6-byte field atoffset X'FF2' in the buffer itself. The layout of thebuffer is described by the DSNDLCID mapping macro.The header of each record within the buffer isdescribed by the DSNDLRH mapping macro. Locate thebuffer that contains the log RBA from the message andfind the damage by referring to the description of thereason code later in this book.

DSNJ014I TERMINAL ERROR ccc IN BUFFERrrr AFTER ACTIVE LOG WRITE.

ExplanationA scan of the log output buffer, after writing to theCOPY 1 active log data set and before writing to COPY2, detected an inconsistency in the log data. 'ccc' is theabend reason code associated with the SDUMP that isproduced. 'rrr' is the log RBA at which the error wasdetected.

System actionDb2 will terminate with a dump, and will not write thedamaged buffer to the COPY 2 data set.


System programmer responseThe block containing the indicated log RBA may bedamaged. The buffer was found to be in error at thecompletion of the write to the COPY 1 data set of theactive log.

If dual active logs are being used, use print log map(DSNJU004) to list the active log data sets for bothcopies of the active log. Find the COPY 2 data set withthe corresponding RBA, and copy that data set (usingaccess method services REPRO) to the COPY 1 dataset. Start Db2.

If only a single active log is used, contact the IBMsupport center for assistance. An attempt to start Db2may succeed if the damage to the buffer occurred aftercompletion of the write to DASD.

Problem determinationIn the Db2 formatted block section of the dump, locatethe chain of LBCE blocks. Those are log buffer controlelements, and each LBCE controls one 4KB log outputbuffer. LBCEBUFF, at offset X'20' in the LBCE points tothe buffer, which is always on a 4KB boundary. The logRBA of the first byte of the buffer is in a 6-byte field atoffset X'FF2' in the buffer itself. The layout of the

buffer is described by the DSNDLCID mapping macro.The header of each record within the buffer isdescribed by the DSNDLRH mapping macro. Locate thebuffer that contains the log RBA from the message andfind the damage by referring to the description of thereason code later in this book.

DSNJ015I CSRONLY PROHIBITS LOGALTERATIONS. RECORD rrrCREATED .... REPLY Y TO USE, NTO CANCEL.

ExplanationDuring Db2 startup, the log manager found an inactiveconditional restart control record in the bootstrap dataset. Because this control record indicates CSRONLY, nolog data sets will be modified. If log truncation wasspecified, it will be simulated. Only the first phase ofrestart (current status rebuild) will be performed. Thehexadecimal identifier (rrr) and creation timestamp(yy.ddd hh:mm) identify the record found.

System actionA 'Y' reply will continue the conditional restart. A 'N'reply will terminate Db2 startup.

Operator responseTo continue this CSRONLY processing, reply 'Y' to thismessage. If you are not sure, contact the systemprogrammer.

System programmer responseThe conditional restart control record will not bedeactivated at the end of the CSRONLY processing. Todeactivate this record, either cancel this record orcreate a new record. If you suspect an error in Db2,you might need to report the problem. For informationabout identifying and reporting the problem, seeCollecting diagnostic data (Collecting data). for moreinformation.

DSNJ016E csect-name WARNING - SYSTEMCHECKPOINT PROCESSOR MAYHAVE STALLED. LASTCHECKPOINT WAS TAKEN date-time.

ExplanationWhile switching active log data sets, Db2 found thatthere has not been a system checkpoint taken sincethe last time Db2 switched active log data sets. date-time is the date and time of the last systemcheckpoint. There should be at least one systemcheckpoint on each log data set.



System actionDb2 continues processing. If statistics class 3 is active,IFCID 0335 is written.


This message is deleted when a system checkpoint istaken.

System programmer responseThis message might be an indication that the systemcheckpoint processor may no longer be functioning.This situation can result in a very long restart if loggingcontinues without a system checkpoint. You shouldmonitor system checkpoint activity very closely. Youcan use the -DISPLAY LOG command or run the PrintLog Map utility (DSNJU004) to display the most recentcheckpoint. If Db2 continues logging beyond thedefined checkpoint frequency, you should quiesceactivity and terminate Db2 to minimize the restarttime.

Prior to terminating Db2, obtain a dump of the Db2address spaces for problem determination.

DSNJ017E csect-name WARNING - OFFLOADTASK HAS BEEN ACTIVE SINCEdate-time AND MAY HAVESTALLED.

ExplanationWhile switching active log data sets, Db2 found thatthe offload task has been active since the last timeDb2 switched active log data sets. The offload taskbegan archiving an active log data set at date-time. Ifactive log switching is occurring rather frequently,repetitive DSNJ017E warnings might be suppressed.

System actionDb2 continues processing. If statistics class 3 is active,IFCID 0335 is written. This message will be deletedwhen the offload task completes the archive process.


System programmer responseThis may be an indication that there may be anoutstanding tape mount request or that the offloadtask may no longer be functioning. This situation canresult in a log-full situation if Db2 can not archive logdata sets when they fill. You should reply to any tapemount requests and monitor offload activity veryclosely. You can issue the -DISPLAY LOG command to

display the status of the offload task, and the -ARCHIVE LOG CANCEL OFFLOAD command can beused to terminate and restart the offload process.

Prior to terminating the offload task, obtain a dump ofthe Db2 MSTR address space for problemdetermination.

DSNJ020I csect-name RECEIVED REPLY OF NTO msg-num. SUBSYSTEMSTARTUP IS TERMINATED.

ExplanationThe operator chose to terminate Db2 startup byanswering 'N' to 'msg-num'.

System actionDb2 will not restart.

Operator responseTo restart Db2, follow the 'operator response' of 'msg-num'.

DSNJ030I RBA RANGE start-rba TO end-rbaNOT AVAILABLE IN ACTIVE LOGDATA SETS

ExplanationPrevious errors have made the active log data sets thatcontain the relative byte address (RBA) range reportedin the message unavailable to Db2. The status of theselogs is STOPPED in the bootstrap data set (BSDS).

System actionDb2 terminates with a dump.


System programmer responseThe log RBA range must be available for Db2 to berecoverable. Correct previous errors and restore theactive log data set(s) that contain the RBA rangereported in the message.

• If the log data sets are recoverable, the active logdata set inventory in the BSDS must be modified toreset the STOPPED status.

1. Use the print log map (DSNJU004) utility toobtain a copy of the BSDS log inventory.


2. Use the change log inventory (DSNJU003) utilityto delete the active log data sets that are markedSTOPPED, by using DELETE statements.

3. Add the data sets again by using NEWLOGstatements of the DSNJU003 utility. The startingand ending RBA for each active log data set mustbe specified on the NEWLOG statements.

• If the log data sets are not recoverable, conditionallyrestart Db2.

Problem determinationExamine previous messages to determine the reasonthe active log data sets are unavailable to Db2.

Related conceptsRecovering from BSDS or log failures duringrestart (Db2 Administration Guide)Conditional restart (Db2 Administration Guide)Related tasksWhat to do before RBA or LRSN limits arereached (Db2 Administration Guide)Related referenceDSNJU003 (change log inventory) (Db2 Utilities)DSNJU004 (print log map) (Db2 Utilities)Related informationRecovering from active log failures (Db2Administration Guide)Recovering from archive log failures (Db2Administration Guide)

DSNJ031I csect-name WARNING -UNCOMMITTED UR HAS WRITTENnumber LOG RECORDS -CORRELATION NAME =correlation-name CONNECTION ID= connection-id LUWID = logical-unit-of-work-id=token PLAN NAME= plan-name AUTHID =authorization-id END USER ID =user-id TRANSACTION NAME =transaction-name WORKSTATIONNAME = workstation-name

ExplanationA unit of recovery (UR) has reached the thresholdnumber of log records that were written without acommit or rollback operation. This threshold wasdefined during installation in subsystem parameterURLGWTH.


numberThe cumulative number of log records that werewritten since the beginning of the UR.

correlation nameThe correlation name that is associated with theUR.

connection-idThe connection ID that is associated with the UR.

logical-unit-of-work-idThe logical unit of work ID. An asterisk (*) denotesthat the thread originated at the local site.

This value consists of a fully qualified LU networkname followed by a period and an LUW instancenumber. The LU network name consists of a one-to eight-character network ID, a period, and a one-to eight-character network LU name. The LUWinstance number consists of 12 hexadecimalcharacters that uniquely identify the unit of work.


plan-nameThe plan that is associated with the UR.

authorization-idThe authorization ID that is associated with theUR.

user-idThe user ID that is associated with the UR, ifknown. Otherwise, an asterisk (*).

transaction-nameThe transaction that is associated with the UR, ifknown. Otherwise, an asterisk (*).

workstation-nameThe workstation host name that is associated withthe UR, if known. Otherwise, an asterisk (*).

System actionProcessing continues. If statistics class 3 is active,IFCID 0313 is written.

This message is repeated each time the threshold isreached.

System programmer responseConsult with the application programmer to determineif this UR is problematic.

If an application program caused the UR to reach itsthreshold number of log records, you can use CANCELTHREAD (token) to cancel the UR. If you cancel anuncommitted UR, Db2 rolls back the changes. Theamount of time that is required for this process




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_conditionalrestart.html





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoveractivelogfailures.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverarchivelogfailures.html


depends on the amount of work that was done by theUR.

Programmer responseEnsure that the application commits frequentlyenough, or consult with your Db2 administrator aboutincreasing the threshold number of log records. Usethe URLGWTH subsystem parameter.

Related tasksDisplaying threads by LUWID (Db2Administration Guide)Programming for concurrency (Db2Performance)Related referenceUR LOG WRITE CHECK field (URLGWTHsubsystem parameter) (Db2 Installation andMigration)

DSNJ032I csect-name alert-level-APPROACHING END OF THE LOGRBA RANGE OF maximum-value.CURRENT LOG RBA IS current-level

ExplanationThe current log RBA is approaching the end of the logRBA range. The current log RBA should not be allowedto advance to the maximum-value.


alert-levelThe type of alert, based on the current log RBAlevel:WARNING

The current log RBA reachedx'F00000000000' for the 6-byte RBA format orx'FFFFFFFF000000000000' for the 10-byteRBA format.

CRITICALThe current log RBA value reachedx'FFFF00000000' for the 6-byte RBA format orx'FFFFFFFFFF0000000000' for the 10-byteRBA format.

maximum-valueThe value is x'FFFFFFFFFFFF' if the log is beingwritten in the 6-byte RBA format. The value isx'FFFFFFFFFFFFFFFFFFFF' if the log is beingwritten in the 10-byte RBA format.

current-levelThe current log RBA value.

System actionDb2 continues processing if the alert-level value isWARNING or if Db2 is restarting. Otherwise, Db2terminates with reason code 00D10251.

Any attempt to restart Db2 in general access mode,following the termination will cause Db2 to restart inlight mode, and Db2 will shut down after restartcompletes the recovery of the incomplete units-of-recovery.



If Db2 terminates and restarts in light mode, wait untilit completes the recovery of incomplete units-of-recovery, and then restart it in ACCESS(MAINT) modeto recover any indoubt units of recovery, start any tablespaces in a restricted state such as LPL or GRECP, orterminate any utilities that are in progress.

System programmer responseIf the Db2 log is using the 6-byte RBA format, convertthe BSDS data sets to support the 10-byte RBAformat. Convert all catalog and directory page sets tothe extended format as soon as possible.

If the log is using the 10-byte RBA format, use thefollowing information to determine when to reset thelog, and how to reset it.

Information on resetting the log RBA:

What to do before RBA or LRSN limits are reached(Db2 Administration Guide)Resetting the log RBA value in a non-data sharingenvironment (6-byte format) (Db2 AdministrationGuide)Resetting the log RBA value in a data sharingenvironment (6-byte format) (Db2 AdministrationGuide)

Related conceptsRestart light (Db2 Data Sharing Planning andAdministration)Related tasksStarting a table space or index space that hasrestrictions (Db2 Administration Guide)Related reference-TERM UTILITY (Db2) (Db2 Commands)-START DATABASE (Db2) (Db2 Commands)DSNJCNVT (Db2 Utilities)Related information00D10251 (Db2 Codes)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_displaythreadbyluwid.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_programapps4concurrency.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_urlgwth.html





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_subsystemendrba.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_subsytemdatashrrba.html





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_starttableorspacewithrestrictions.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_termutility.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_dsnjcnvt.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00d10251.html

DSNJ033E csect-name THE LOG RBA MUST BERESET BEFORE THE END OF THELOG RBA RANGE IS REACHED

ExplanationThis message is issued with the DSNJ032I message toindicate that Db2 is approaching the end of the logRBA range.


System actionThe alert-level value in the accompanying messageDSNJ032I determines the system action.

User response:See the description of message DSNJ032I forinformation and recommended actions.

Related informationDSNJ032Icsect-name alert-level- APPROACHING END OFTHE LOG RBA RANGE OF maximum-value.CURRENT LOG RBA IS current-level

DSNJ034I csect-name alert-level-APPROACHING END OF THE LRSNRANGE. CURRENT LRSN IScurrent-lrsn

ExplanationThe LRSN for the data-sharing group is approachingthe maximum value. If the Db2 log is using the 6-byteRBA format, the maximum LRSN is x'FFFFFFFFFFFF'.If the Db2 log is using the 10-byte RBA format, themaximum LRSN is x'FFFFFFFFFFFFFFFFFFFF'.


alert-levelThe type of alert, based on the current LRSN value:WARNING

The LRSN range will reach its limit in one yearor less.

CRITICALThe LRSN range will reach its limit in one weekor less.

current-lrsnThe current LRSN value.

System actionDb2 continues processing if the alert-level value isWARNING or if Db2 is restarting. Otherwise, Db2terminates with reason code 00D10251.

Any attempt to restart Db2 in general access mode,following the termination, causes Db2 to restart inlight mode and to shut down after restart completesthe recovery of the incomplete units-of-recovery.



If Db2 terminates and restarts in light mode, wait untilit completes the recovery of incomplete units-of-recovery, and then restart it in ACCESS(MAINT) modeto recover any indoubt units-of-recovery, start anytable spaces in a restricted state such as LPL orGRECP, or terminate any utilities that are in progress.

System programmer responseIf the Db2 subsystem is using the 6-byte RBA logformat, convert to the 10-byte RBA log format. Thisformat allows the use of 10-byte LRSN values as well.If the database objects are in 6-byte basic format, theyneed to be converted to 10-byte extended format. Ifthe Db2 subsystem is using the 10-byte RBA logformat, contact IBM Support.

Related conceptsRestart light (Db2 Data Sharing Planning andAdministration)Related tasksStarting a table space or index space that hasrestrictions (Db2 Administration Guide)Related reference-TERM UTILITY (Db2) (Db2 Commands)-START DATABASE (Db2) (Db2 Commands)Related information00D10251 (Db2 Codes)

DSNJ035E csect-name ACTION MUST BETAKEN BEFORE THE END OF THELRSN RANGE IS REACHED

ExplanationThis message is issued with the DSNJ034I message toindicate that Db2 is approaching the end of the LRSNrange.






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_termutility.html




System actionThe alert-level value in the accompanying messageDSNJ034I determines the system action.

User response:See the description of message DSNJ034I forinformation and recommended actions.

Related informationDSNJ034Icsect-name alert-level- APPROACHING END OFTHE LRSN RANGE. CURRENT LRSN IS current-lrsn

DSNJ050I LOAD MODULE DSNJL003 DOESNOT HAVE RMODE(24) ATTRIBUTE

ExplanationThe named load module was not link edited with therequired RMODE(24) attribute.

System actionDb2 startup is terminated.

Operator responseNotify the system programmer of the failure.

System programmer responseVerify that all installation and maintenance activitiesagainst this module were executed using SMP. Verifythat the JCLIN for SMP includes the correct RMODEcontrol statement, and that the Linkage Editorprovided with the Data Facility Product (DFP) for theversion of MVS being used was invoked by SMP for thelink edits. Correct the procedure or JCL which causedthe error and rerun the necessary SMP jobs.

Problem determinationThe MVS service aid AMBLIST provides Linkage Editormodule attributes in the summary section of theLISTLOAD function output.

DSNJ070I csect-name ARCHIVE LOG DSNPREFIX NOT IN PROPER FORMATTO RECEIVE TIMESTAMP DATA.TIMESTAMPING OF dsnnameBYPASSED

ExplanationBy way of a ZPARM parameter, the user has specifiedthat the date and time of creation of an archive logdata set be included as part of the archive log data setname (DSN). To accomplish this, the Db2 subsystemrequires that the length of the archive log data setname prefix not exceed 19 characters if using thestandard DATE format (YYDDD), or 17 characters ifusing the extended DATE format (YYYYDDD). If theprefix requirement is not met, this message is issuedjust prior to the allocation of the archive log data setspecified in the message.

System actionThe archive log data set will be allocated using thearchive log prefix. However, the archive log DSN willnot contain the date and time as the user requested.


System programmer responseThe values of TSTAMP and ARCPFXn subsystemparameters are not consistent with one another andmust be changed.

Related referenceTIMESTAMP ARCHIVES field (TSTAMPsubsystem parameter) (Db2 Installation andMigration)COPY 1 PREFIX field (ARCPFX1 subsystemparameter) (Db2 Installation and Migration)COPY 2 PREFIX field (ARCPFX2 subsystemparameter) (Db2 Installation and Migration)

DSNJ071I csect-name TIMER FAILURECAUSED TIMESTAMPING OFARCHIVE dsname TO BEBYPASSED

ExplanationBy way of a ZPARM parameter, the user has specifiedthat the date and time of creation of an archive logdata set be included as part of the archive log data setname (DSN). However an attempt to get the currentdate and time from the system failed. This message isissued just prior to the allocation of the archive logdata set specified in the message.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_tstamp.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_arcpfx1.html




System actionThe archive log data set will be allocated using thearchive log prefix. However, the archive log DSN willnot contain the date and time as the user requested.

DSNJ072E ARCHIVE LOG DATA SET dsnameHAS BEEN ALLOCATED TO NON-TAPE DEVICE AND CATALOGED.ZPARM CATALOG OPTION OF 'NO'HAS BEEN OVERRIDDEN.

ExplanationThe following archive log subsystem parametersspecified that all archive log data sets are to beallocated to a non-tape device and uncataloged:

• The UNIT subsystem parameter specified a non-tapedevice.

• The CATALOG subsystem parameter value wasspecified as NO.

However, Db2 requires that all archive log data setsthat are allocated to non-tape devices must becataloged.

dsnameThe archive log data set.

System actionThe specified archive log data set was allocated to anon-tape device, as specified by the UNIT subsystemparameter, and was cataloged. The specified CATALOGsubsystem parameter value of NO was overridden. TheBSDS reflects that the data set was cataloged.


System programmer responseChange the values of the UNIT and CATALOGsubsystem parameters so that they are consistent withone another

Related referenceDEVICE TYPE 1 field (UNIT subsystemparameter) (Db2 Installation and Migration)CATALOG DATA field (CATALOG subsystemparameter) (Db2 Installation and Migration)

DSNJ073I LOG ARCHIVE UNIT ALLOCATIONFAILURE DETECTED, RETURNCODE=nnnn. ALLOCATION OROFFLOAD OF ARCHIVE LOG DATASET MAY FAIL.

ExplanationWhile building the SVC99 text entries to dynamicallyallocate a new archive log data set, a unit allocationfailure was detected. This message is only generatedwhen a trace for IFCID 320 is active. The reason code,indicated by nnnn in the message, further clarifies theproblem as follows:4 (X'04')

The device type (unit name) on which the archivelog data set is to be allocated is specified by theuser in the Db2 system parameters. No UCBs couldbe found for the device type (unit name).

8 (X'08')The device type (unit name) on which the archivelog data set is to be allocated is specified by theuser in the Db2 system parameters. This devicetype (unit name) could not be found in the MVSeligible device table (EDT).

32 (X'20')Db2 was able to obtain a list of devicescorresponding to the device type (unit name)specified in ZPARMs. However, it was determinedby Db2 that this list contained a mixture of tapeand nontape devices.

40 (X'28')The device type (unit name) specified by the userin ZPARMs is valid. However, no devices arecurrently associated with the given device type(unit name).

44 (X'2C')The device type (unit name) specified by the userin ZPARMs is valid. However, no DASD volumes areavailable with a volume use attribute of 'storage'.

48 (X'30')The CVT indicates that UCB services are notavailable.

System actionThis message is issued by Db2 after the SVC99 textentries are built, but prior to the allocation of the newarchive log data set. As a result of the error, thedynamic allocation of the archive log data set will beattempted using standard default values. The standarddefault values are generally acceptable; however, theallocation may fail or the subsequent offload mayproduce undesirable processing results. For example:

• A return code of 4 or 44 (X'2C') will foretell anallocation error (DSNJ103I) when the SVC99 isissued for the archive data set.

• Offload processing to tape may fail. Db2 uses avolume count of 20 when allocating to tape, anduses the standard MVS volume count default of 5volumes when writing to nontape devices. In the


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_unit.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_unit.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_catalogarvp.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_catalogarvp.html

case of most of the above errors, it would beimpossible for the Db2 subsystem to determine thedevice type on which the data set is to be allocated.Therefore, the standard MVS default is assumed forthe volume count. If the data set is successfullyallocated to a tape device, and the volume of data issuch that more than five volumes will be used for thearchive data set, the offload processing will receivean MVS ABEND 837-08 with message IEC028I whenattempting to write to the sixth tape volume.

• Offload processing to a direct access device may fail.When allocating a new archive log data set on adirect access device, the Db2 subsystem will use aunit count to facilitate multivolume archive datasets. With most of the above errors, it may beimpossible for the Db2 subsystem to correctlydetermine the type of device on which the data set isto be allocated. Therefore, the standard default (1) isassumed for the unit count. If the data set issuccessfully allocated to a direct access device, andduring the offload processing it becomes necessaryto extend the data set to another device, the offloadprocessing will receive an MVS B37 (out of space)ABEND, and the archive log data set will bedeallocated.


System programmer responseThe required action is based on the return codeindicated in the message.4 (X'04') or 8 (X'08')

The most likely cause is an incorrect specificationin the archive log ZPARMs (DSNTIPA panel).Correct the DEVICE TYPE field. If the DEVICE TYPEfield from the archive log ZPARMs appears to becorrect, check the EDT to ensure that the esotericor generic unit name specified in the ZPARMs isactually in the EDT. Subsequent offload processingwill archive the log data which could not bepreviously archived due to the allocation failure(DSNJ103I).

32 (X'20') or 40 (X'28')To correct this situation, change the archive logDEVICE TYPE ZPARM to use a device type (unitname) which contains homogenous devices, ormodify the device list associated with the devicetype (unit name) via a system generation to supplya list of homogenous devices.

44 (X'2C')To correct this situation, issue an MVS mountcommand to change the volume use attribute of amounted 'private' volume to 'storage'. If this is a

recurring problem, a system generation may berequired to add permanently resident volumeswith a volume use attribute of 'storage' to theesoteric or generic unit, or ZPARMs may have to bechanged to use a different esoteric or generic unitname for the DEVICE TYPE (on the DSNTIPAinstallation panel).

48 (X'30')Migrate the operating system to a release levelthat supports UCB services.

DSNJ096E csect-name CRCR ENDLRSN RBAVALUE OF rrr IS INVALID, NOTRUNCATION WILL OCCUR

ExplanationTruncation cannot take place because the RBA valuespecified on the active CRCR record is not equal to theRBA of a log record. rrr is the ENDLRSN specified in theactive record. The ENDLRSN RBA value must matchthe start of a log record in a non-data sharingenvironment.



System programmer responseConfirm that the ENDLRSN value specified in theConditional Restart control record is correct. Run theChange Log Inventory (DSNJU003) utility with theCRESTART CANCEL parameters to cancel theconditional restart. If log truncation is needed, run theDSNJU003 utility with the correct ENDLRSN value.Restart Db2.

DSNJ098E csect-name CRCR ENDLRSN OF rrrIS xxx THAN ANY KNOWN yyyy,NO TRUNCATION WILL OCCUR

ExplanationTruncation cannot take place because the CRCRENDLRSN is not in the range of LRSN or RBA valuesknown to either the active or archive logs. rrr is the endLRSN specified in the active record. xxx is replaced byeither HIGHER or LOWER. In a data sharingenvironment, if xxx is HIGHER, the CRCR ENDLRSN ishigher than the LRSN of the last record written to thelog data sets. If xxx is LOWER, the CRCR ENDLRSN islower than the starting LRSN of the oldest archive dataset. yyyy is replaced by LRSN. In a non-data sharing


environment, if xxx is HIGHER, the CRCR ENDLRSN ishigher than the RBA of the last record written to thelog data sets. If xxx is LOWER, the CRCR ENDLRSNvalue is an RBA value that is lower than the startingLRSN of the oldest archive data set. yyyy is replaced byRBA.



System programmer responseConfirm that the ENDLRSN value specified in theConditional Restart control record is correct. If it is notcorrect, run the Change Log Inventory (DSNJU003)utility with the CRESTART CANCEL parameters tocancel the conditional restart. If log truncation isneeded, run the DSNJU003 utility with the correctENDLRSN. Restart Db2.

DSNJ099I LOG RECORDING TO COMMENCEWITH STARTRBA=...

ExplanationThis message is generated when the log manager isinitialized during Db2 startup. The value specified bythe STARTRBA=value keyword is the RBA of the nextbyte of log data to be recorded in the Db2 active logdata set(s). This information may later be needed for aconditional restart.

This message is preceded by one DSNJ001I message(if single logging) or two DSNJ001I messages (if duallogging).


DSNJ100I csect-name ERROR OPENINGBSDSn DSNAME=..., ERRORSTATUS=eeii

ExplanationLog manager initialization or the -RECOVER BSDScommand could not open the specified bootstrap dataset (BSDS). BSDSn matches the ddname in the logstartup JCL of the data set that cannot be opened. Thevalue of n is 1 or 2. If you suspect an error in Db2, youmight need to report the problem. For information

about identifying and reporting the problem, seeCollecting diagnostic data (Collecting data). forinformation about recovery from BSDS or log failures.

System actionWhen this error occurs at initialization time, Db2startup must be terminated, because the log data setscannot be determined and allocated without the BSDS.When this error occurs during -RECOVER BSDSprocessing, the command is terminated, and thesystem continues in single BSDS mode.


System programmer responseRecover the BSDS that cannot be opened. Normally, ifdual BSDSs are being used, recovery consists ofmaking a copy of the remaining good BSDS.

Problem determinationThe 'error status' contains the VSAM open return codein 'ee', and the VSAM open reason code in 'ii'. Refer toz/OS DFSMS: Macro Instructions for Data Sets for a listof the VSAM open return codes and reason codes, andthe steps required to take corrective action.

DSNJ101E csect-name CRCRERBA OF rrr ISxxx THAN ANY KNOWN RBA, BUTCOLD START WAS NOT SPECIFIED

ExplanationTruncation cannot take place because the CRCR endRBA is not in the range of RBA values known to eitherthe active or archive logs. 'rrr' is the end RBA specifiedin the active record. 'xxx' is replaced by either HIGHERor LOWER. If HIGHER is the case, the CRCRERBA ishigher than the end RBA of the most recent active logdata set. LOWER means the CRCRERBA is lower thanthe starting RBA of the oldest archive data set.



System programmer responseMost likely, the archive log data set that contained therequested RBA has been deleted from the bootstrap



data set (BSDS) by the change log inventory(DSNJU003) utility. Locate the output from an old PrintMap run, and identify the data set that contains themissing RBA. If the data set has not been reused, runthe DSNJU003 utility to add this data set back into theinventory of log data sets. Restart Db2.

DSNJ102I LOG RBA CONTENT OF LOG DATASET DSNAME=..., STARTRBA=...,ENDRBA=..., DOES NOT AGREEWITH BSDS INFORMATION

ExplanationThe log RBA range shown in the BSDS for the specifieddata set does not agree with the content of the dataset. This message indicates that the change loginventory (DSNJU003) utility was used incorrectly orthat a down-level volume is being used.

System actionDb2 startup processing is terminated.


System programmer responseUse the print log map (DSNJU004) and change loginventory (DSNJU003) utilities to make the BSDSconsistent with the log data sets.

DSNJ103I csect-name LOG ALLOCATIONERROR DSNAME=dataset-name,ERROR STATUS=status-indicator,SMS REASON CODE=ssssssss

ExplanationThe log manager encountered an error while itattempted to allocate the specified active or archivelog data set.



status-indicatorThe error reason code that is returned by MVSdynamic allocation (SVC99). This value consists ofa 2-byte error code (S99ERROR) followed by a 2-byte information code (S99INFO) from the SVC99request block.

ssssssssIf available, more SMS reason code informationfrom S99ERSN, which is a field of S99RBX.ssssssss is displayed if the S99ERROR codeindicates an SMS allocation error (97xx).

This message might be preceded by messageDSNJ073I.

System actionFor active log data sets, if the error is encounteredduring log manager initialization, Db2 startup isterminated. If two copies of the active log data setsare defined, this message is displayed only once.

For archive log data sets, if two copies of the archivelog data sets are defined, processing continues on theremaining archive log data set.


System programmer responseIf the status-indicator value is '17080000', the sitemight have one or more active log data sets defined inthe BSDS, but not allocated on DASD. To correct thesituation, print the contents of the current active logdata set inventory by using the print log map(DSNJU004) utility. Then, take one of the followingactions:

• For each active log data set that is listed in the BSDS,but not allocated on DASD, allocate the active logdata set by using access method services. Theaccess method services command syntax for activelog data sets can be found in installation jobDSNTIJIN.

• Use the DSNJU003 utility DELETE statement todelete the errant active log data set name. Then, usethe DSNJU003 utility NEWLOG statement to add thecorrect name to the active log data set inventory. Thename that is specified on the NEWLOG statementmust be the same as the name of the actual Db2active log data set that is allocated on DASD.

If the problem occurred because the MVS task I/Otable (TIOT) did not have enough space, an allocationerror occurs. In this case, perform the followingactions to maximize the size of the TIOT and tominimize the amount of TIOT space that each data setuses:

1. Set the MVS TIOT size to 64K in the ALLOCxxPARMLIB member.

2. Specify NON_VSAM_XTIOT=YES in the DEVSUPxxPARMLIB member to enable Db2 to use the MVS


extended task I/O table (XTIOT) when allocatingoffload data sets.

3. Specify a dynamic volume count (DVC) of 0 for anySMS data set class that is used to allocate a Db2BSDS, active log, or secondary log data set.

4. Reallocate any existing BSDS, active log, orsecondary log data sets that were allocated with aDVC greater than 0.

If the problem occurred during Db2 initialization andthat data set is an active log data set, take one of thefollowing actions:

• Resolve the error (status-indicator) that is associatedwith the active log data set

• Provide another copy of the active log data set byusing access method services (AMS)

• Update the BSDS by using the change log inventory(DSNJU003) utility

• Restart Db2

For archive log data sets, take one of the followingactions:

• If the problem occurred during allocation with theintent to write the data set, no immediate action isrequired. However, failure to resolve the error(status-indicator) might eventually cause theavailable space in the active log to be exhausted(DSNJ111E), because all future offloads might faildue to the same error.

• If the problem occurred during allocation with theintent to read the data set, determine the problem.Use the DSNJU003 utility DELETE statement todelete the archive log data set from the BSDSarchive log inventory. Then, use the DSNJU003utility NEWLOG statement to add the data set backto the archive log inventory with the correct volumeand device.

Related conceptsRecovering from BSDS or log failures duringrestart (Db2 Administration Guide)Related referenceInterpreting DYNALLOC return codes (MVSProgramming Authorized Assembler ServicesReference)S99RBX fields (MVS Programming AuthorizedAssembler Services Reference)DSNJU003 (change log inventory) (Db2 Utilities)Related informationRecovering from active log failures (Db2Administration Guide)Recovering from archive log failures (Db2Administration Guide)DSNJ073I

LOG ARCHIVE UNIT ALLOCATION FAILUREDETECTED, RETURN CODE=nnnn. ALLOCATIONOR OFFLOAD OF ARCHIVE LOG DATA SET MAYFAIL.DSNJ111EOUT OF SPACE IN ACTIVE LOG DATA SETS

DSNJ104I csect-name RECEIVED ERRORSTATUS nnn FROM macro-nameFOR DSNAME dsname

ExplanationDb2 encountered an error while issuing macro macro-name. Unless macro-name is OPEN, and the targetdata set is a non-VSAM data set, the error status is thereturn code from the specified macro call.

More information about each error status nnn valuefollows:

• If macro-name is OPEN and the target data set is aVSAM data set, nnn is the return code in the errorfield of the access method services control block.Refer to the appropriate VSAM publication for adefinition of these values. Message DSNJ104I ispreceded by an IEC161I message that defines theerror that occurred.

• If macro-name is OPEN and the target data set is anon-VSAM data set, nnn is zero. Message DSNJ104Iis preceded by an IEC143I message that defines theerror that occurred.

• If macro-name begins with MMSRV, nnn is the errorinformation that is returned by media managerservices. If an MMSRV CATUPDT failure occursduring truncation an active log data set, the log dataset is unavailable to Db2, and the status of the logdata set is flagged as STOPPED in the BSDS.Message DSNJ104I is preceded by an IEC161Imessage for a VSAM OPEN error, and by an IEC251Imessage for a VSAM CLOSE error.

• If macro-name is PROTECT and the target data set isan archive log data set, nnn is from DADSMPROTECT. Refer to the appropriate z/OS publicationfor a description of the MMSRV return codes.

• If macro-name is CLOSE, and the target data set isan archive log data set, nnn is the TCB completioncode for an abend received during CLOSEprocessing. This abend is normally preceded by anIEC210I or IEC212I message that defines the error.

• If macro-name is EDTINFO or UCBLOOK, the firsttwo bytes of nnn contain the return code and thesecond two bytes of nnn contain the reason codethat are returned from the call.

If you suspect an error in Db2, you might need toreport the problem. For information about identifying







http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa800/s99rbxf.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa800/s99rbxf.htm






and reporting the problem, see Collecting diagnosticdata (Collecting data).

System actionIf this condition is encountered during log managerinitialization, Db2 startup is terminated. If the erroroccurs later, and the data set is needed for offload orfor input operations, Db2 processing continues. If asecond copy of the data is available, Db2 attempts toallocate and open the second data set.

If the data set is needed as an active log data set, thelog manager attempts to retry the failing request. Ifthe retry fails, the Db2 subsystem is terminated.


System programmer responseIf the error occurred during initialization, correct theproblem so that the data set is available, or provideanother copy of the data set, and change the BSDSdata sets to point to the new data set.

If the error occurred during Db2 processing, review thereturn code. Take the appropriate action to correct theproblem so that the data set can be used at a latertime, or use the change log inventory utility(DSNJU003) to remove the data set entry from theBSDS.

If the error was received from PROTECT, there mightbe a problem with the PASSWORD data set. Refer tothe appropriate DADSM publication to determine thecause of the problem. When the problem has beencorrected, add the archive log data sets that receivedthe error to the PASSWORD data set. If you do not addthese archive log data sets to the PASSWORD data set,archive read fails during OPEN of the data sets.

If the error was received from EDTINFO or UCBLOOK,and the allocation of the archive log data set fails,verify that the archive UNIT names are correct in theUNIT and UNIT2 subsystem parameters.

DSNJ105I csect-name LOG WRITE ERRORDSNAME=dataset-nameLOGRBA=rba-value, ERRORSTATUS=ccccffss

ExplanationThe log manager encountered a write error in thespecified active log data set.


If csect-name is DSNJW107 or DSNJW127, theerror occurred when writing the log buffers to anactive log data set.

If csect-name is DSNWJ207, the error occurredwhile preformatting the next control area beforewriting log data to it.


rba-valueThe RBA value in the log where the write erroroccurred.

ccccffssThe error information that is returned by mediamanager.cccc

A 2-byte return code that describes the error.ff

A 1-byte code that defines the functionalroutine that detected the error.

ssThe 1-byte status code that defines a generalcategory of error.

System actionIf the dual active logging option is selected, the logmanager switches to the next data set for this copy. Ifthe next data set is not ready, the log managertemporarily enters single logging mode and allocates areplacement data set for the one that encountered theerror. Dual logging is resumed as soon as possible.

If single active logging option is selected and the nextdata set is not ready, the log manager waits for thatdata set to be available. In this case, log writing isinhibited until the replacement is ready for output.


System programmer responseSee the information for the media manager returncode that is indicated in ccccffss.

Related referenceMedia Manager return codes

DSNJ106I LOG READ ERRORDSNAME=dsname-value,LOGRBA=log-rba-value, ERRORSTATUS=ccccffss




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idar100/mmdi2.htm

ExplanationThe log manager encountered an error while readingan active log data set. The ERROR STATUS valuecontains the error information returned by the mediamanager in the form ccccffss, where ccccis a 2-bytereturn code that describes the error, ff is a 1-byte codethat defines the functional routine that detected theerror, and ss is the 1-byte status code that defines ageneral category of error.

System actionIf another log data set contains the data, the logmanager attempts to read the data from the alternatesource. If an alternate source is not available, the logmanager returns a read error return code to theprogram requesting the log data.


System programmer responseIf the site is using dual logging, the requested RBA wasprobably retrieved from the corresponding dual activelog data set, and no immediate response is necessary.However, if this error occurs frequently, or if the site isusing single logging, immediate attention may berequired.

Take corrective action based on the media managerreturn codes.

It might be necessary to replace the bad data set witha new data set containing the log data, and to updatethe BSDSs to reflect the new data set using the changelog inventory (DSNJU003) NEWLOG operation.

This message can also be issued as the result of apossible user error. If the data set name associatedwith the DSNAME value is missing, and the ERRORSTATUS value contains '00180408' or '00100408',then the site is using dual logging, but only one set ofactive log data sets are defined in the BSDS. To resolvethis condition, take one of the following actions:

• Define a second set of active log data sets usingaccess method services (if they are not definedalready), and update the BSDS log inventory usingthe DSNJU003 NEWLOG operation.

• To specify single logging, set the value of theTWOACTV subsystem parameter to NO.

Related conceptsRecovering from BSDS or log failures duringrestart (Db2 Administration Guide)Related referencez/OS DFSMSdfp Diagnosis

NUMBER OF COPIES field (TWOACTVsubsystem parameter) (Db2 Installation andMigration)DSNJU003 (change log inventory) (Db2 Utilities)Related informationRecovering from active log failures (Db2Administration Guide)Recovering from archive log failures (Db2Administration Guide)

DSNJ107I READ ERROR ON BSDSDSNAME=name ERRORSTATUS=status

ExplanationThe log manager encountered an error while readingthe specified bootstrap data set. Error Status containsthe VSAM return and feedback codes. It is a 2-bytefield with the first byte containing the hexadecimalreturn code and the second containing thehexadecimal feedback code. Refer to the appropriateMVS publication for a description of VSAM return andreason codes.

If you suspect an error in Db2, you might need toreport the problem. For information about identifyingand reporting the problem, see Collecting diagnosticdata (Collecting data). for information about recoveryfrom BSDS or log failures.

System actionIf dual BSDSs are available, the log manager attemptsto read from the other BSDS. If read from the secondBSDS fails or if there is only one BSDS, an error code isreturned to the log request that caused access to theBSDS.

If read error is detected during start-up, Db2initialization process is terminated to prevent usersfrom operating in a cripple mode. User should takeaction to correct the problem.


System programmer responseIt may be necessary to replace or repair the BSDS,depending on what conditions resulted from the readerror. To replace a BSDS, first delete the bad BSDS,and then define the new BSDS with the same nameand attributes. If a new name is used for the newBSDS, change the log startup JCL to specify the newBSDS name.




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idar100/toc.htm

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_twoactv.html










DSNJ108I WRITE ERROR ON BSDSDSNAME=... ERROR STATUS=...

ExplanationThe log manager encountered an error while writing tothe specified bootstrap data set. Error Status containsthe VSAM return and feedback codes. It is a 2-bytefield with the first containing the hexadecimal returncode and the second containing the hexadecimalfeedback code. Refer to the appropriate VSAMpublication for a description of VSAM return andreason codes.

System actionIf dual BSDSs are available, the log manager enterssingle BSDS mode using the remaining good BSDS.Otherwise, an error code is returned to the log requestthat caused access to the BSDS.


System programmer responseIf dual BSDS mode is being used, execute an offlineaccess method services job to rename the error BSDSand define a new BSDS with the same name. Thenenter the log manager -RECOVER BSDS command toreestablish dual BSDS mode.

If dual BSDS mode is not being used, the Db2subsystem must be shut down, and the BSDS must berecovered from a backup copy. To recover the BSDS,use the change log inventory (DSNJU003) utility.

DSNJ109I OUT OF SPACE IN BSDSDSNAME=...

ExplanationThe specified bootstrap data set does not have anymore space. The operation that encountered the out-of-space condition did not complete properly.

System actionIf dual BSDSs are available, the log manager enterssingle BSDS mode using the remaining good BSDS.Otherwise, an error code is returned to the log requestthat caused access to the BSDS.



System programmer responseIf dual BSDS mode is being used, execute an offlineaccess method services job to rename the full BSDSand define a new, larger BSDS with the same name.Enter the Db2 -RECOVER BSDS command toreestablish dual BSDS mode.

If dual BSDS mode is not being used, the Db2subsystem must be shut down and the BSDSrecovered offline. In this case, execute the sameaccess method services job mentioned above torename the full data set and define a larger data set.Next, execute an access method services REPRO job tocopy the full BSDS into the new BSDS.

DSNJ110E LAST COPYn ACTIVE LOG DATASET IS nnn PERCENT FULL

ExplanationThis message is issued when the last available activelog data set is 5% full, and is reissued after eachadditional 5% of the data set space is filled.

System actionEach time the message is issued, the offloadprocessing is retried. If the situation is not corrected,the active log data space fills to capacity, messageDSNJ111E is issued, and the Db2 online processinghalts.

Operator responseTo clear this condition, steps must be taken tocomplete other waiting offload tasks. Once an activelog data set is made available (reusable) by completingthe offload process for it, the Db2 logging activity cancontinue.

Execute an MVS Display System Requests command (DR,L for example) to determine the outstandingrequests related to the log offload process. Take thenecessary action to satisfy any requests, and permitoffload to continue. If offload fails to completenormally or cannot be initiated, notify the systemprogrammer.

System programmer responseEither correct the problem that is causing the offloadprocess to fail, or add more active log data sets. Thelatter action requires Db2 to be down and the changelog inventory (DSNJU003) utility to be run.


Possible causes for the shortage of active log dataspace are:

• Excessive logging. For example, too many users haverequested logs at the same time or too many utilitieshave specified LOG(YES).

• Delayed or slow offloading. For example, failure tomount archive volumes, incorrect replies to offloadmessages, or slow device speeds.

• Excessive use of the -ARCHIVE LOG command. Eachinvocation of the -ARCHIVE LOG command causesthe Db2 subsystem to switch to a new active log dataset and to initiate an offload of the active log.Although the -ARCHIVE LOG command will not beprocessed when only one active log data set remainsin a copy of the active log (see DSNJ319I), excessiveuse of the command could have consumed all spacein the active log except the current active log datasets.

• Offloads failed. See Operator Response.• Insufficient active log space. See Operator

Response.• Offload task no longer functioning. Issue the -

ARCHIVE LOG CANCEL OFFLOAD command toabnormally terminate and restart the offloadprocess.

DSNJ111E OUT OF SPACE IN ACTIVE LOGDATA SETS

ExplanationDue to delays in offload processing, all available spacein all active log data sets has been exhausted. Db2recovery logging cannot continue.

System actionThe Db2 log manager waits for an available data set.


Operator responseExecute an MVS Display System Requests command (DR,L for example) to ensure that there are nooutstanding requests that are related to the log offloadprocess. Take the necessary action to satisfy anyrequests, and permit offload to continue.

System programmer responseExamine the JES job log for the ssnmMSTR addressspace to determine the cause of the delay. If the delaywas caused by the lack of a resource required foroffload, the necessary resource must be made

available to allow offload to complete and thus permitlogging to proceed.

Related conceptsEffects of interruptions and errors on the offloadprocess (Db2 Administration Guide)Related informationRecovering from temporary resource failure(Db2 Administration Guide)Recovering from active log failures (Db2Administration Guide)Recovering from being out of space in activelogs (Db2 Administration Guide)

DSNJ112E csect-name INSUFFICIENTACTIVE LOG DATA SETS DEFINEDIN BSDS

ExplanationThere are not enough active log data sets defined inthe BSDS to start Db2. This condition usually exists forone of the following reasons.

• Fewer than two data sets are defined for one of theactive log copy sets.

• DSN6LOGP specified TWOACTV=YES in Db2initialization parameters, but data sets for twocopies of active log are not defined in BSDS.

• Fewer than two data sets are available (not flaggedas STOPPED) for one of the active log copy sets.



System programmer responseUse the change log inventory (DSNJU003) utility tomake the number of active log data sets defined in theBSDS consistent with the parameters specified onDSN6LOGP. Log data sets that are flagged as'STOPPED' will not be reused by Db2. These data setsmust be recovered (either redefined or recovered fromthe other copy of the log) and the log data sets mustbe deleted and re-added to the BSDS (usingDSNJU003) with the appropriate RBA's, to clear theSTOPPED status. Restart Db2.

DSNJ113E csect-name log-type log-value NOTIN ANY ACTIVE OR ARCHIVE LOGDATA SET. CONNECTION-ID=aaaaaaaa, CORRELATION-


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_interrupioninoffload.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_interrupioninoffload.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverresourcetemporaryfailure.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverresourcetemporaryfailure.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoveractivelogoutofspace.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoveractivelogoutofspace.html

ID=aaaaaaaa, MEMBER-ID=member-id

ExplanationA request was made to read the log starting at this log-value and log-type (RBA or LRSN). However, the logvalue cannot be found in any active or archive log dataset for the indicated member. The member-id containsthe ID of the data sharing member whose logs werebeing requested at the time of the failure or zero ifdata sharing is not active. The connection andcorrelation IDs identify the user or application thatencountered the problem. Correlation IDs beginningwith '0nn' where 'nn' is a number from 01 to 28,identify system agents. If you suspect an error in Db2,you might need to report the problem. For informationabout identifying and reporting the problem, seeCollecting diagnostic data (Collecting data). forinformation about recovery from log failures.

System actionDepending upon what log record is being read andwhy, this error could result in an abend with a reasoncode of '00D1032A'.


System programmer responseThis error could be a user error. In most cases, thearchive log data set that contained the requested logvalue has been deleted from the bootstrap data set(BSDS) by the change log inventory (DSNJU003) utility.Complete the following steps to correct the error:

• Locate the output from an old print log map run ofthe BSDS for the Db2 member identified by member-id.

• Identify the data set that contains the missing logvalue. If the data set has not been reused, run theDSNJU003 utility to add this data set back into theinventory of log data sets.

• Restart Db2.

DSNJ114I ERROR ON ARCHIVE DATA SET,OFFLOAD CONTINUING WITHONLY ONE ARCHIVE DATA SETBEING GENERATED

ExplanationAn error occurred while accessing one of the archivedata sets being created by offload. Because the dualarchive option is specified, offload is continuing with

the other archive data set. For the RBA range beingoffloaded, there is only one copy of the archive dataset instead of the usual two copies.

System actionOffload produces a single archive data set.

System programmer responseA second copy of this archive log data set can bemade, and the BSDS can be updated with the changelog inventory utility (DSNJU003).

DSNJ115I OFFLOAD FAILED, COULD NOTALLOCATE AN ARCHIVE DATA SET

ExplanationOffload could not allocate or open an archive log dataset. The offload was not performed. If this message ispreceded by message DSNJ103I, the offload data setcould not be allocated. If this message is not precededby DSNJ103I, the offload data set was successfullyallocated, but could not be opened.

System actionOffload will be tried at a later time.


System programmer responseIf the allocation failed with DSNJ103I, review the errorstatus information of message DSNJ103I. Correct thecondition that caused the data set allocation to fail sothat, on retry, the offload can take place.

DSNJ116I ERROR ATTEMPTING TO ADDARCHIVE ENTRY TO BSDS

ExplanationOffload could not add an archive entry to the BSDS.The offload is considered incomplete. The active logdata set is not marked as reusable for new log data.This message is preceded by message DSNJ107I,DSNJ108I, or DSNJ109I.

System actionOffload will be retried at a later time.




System programmer responseRefer to the specific preceding message for action.

DSNJ117I INITIALIZATION ERROR READINGBSDS DSNAME=......, ERRORSTATUS=...

ExplanationThe log manager encountered an error duringinitialization reading from the specified bootstrap dataset. Error status contains the VSAM return andfeedback codes. It is a two byte field with the firstcontaining the hexadecimal return code and thesecond byte containing the hexadecimal feedbackcode. Refer to the appropriate VSAM publication for adescription of VSAM return and reason codes.



System programmer responseDetermine the cause of the read error using the VSAMerror status information provided. Restart Db2.

DSNJ118I LOG INITIALIZATION RECEIVEDRETURN CODE nnn FROMxxxxxxxx MACRO

ExplanationLog manager initialization received a bad return codefrom the named macro.

System actionDb2 initialization is terminated.


System programmer responseDetermine the problem from the documentation onthe named macro and return code. Then takeappropriate steps, and restart the Db2 subsystem.

DSNJ119I BOOTSTRAP ACCESSINITIALIZATION PROCESSINGFAILED

ExplanationDuring log manager initialization, the bootstrap dataset access function was unable to complete itsinitialization process. If you suspect an error in Db2,you might need to report the problem. For informationabout identifying and reporting the problem, seeCollecting diagnostic data (Collecting data). forinformation about recovery from BSDS or log failures.



System programmer responseOne or more error messages describing the specificerror have preceded this message. Refer to thespecific message(s) for error analysis and theappropriate action to take.

DSNJ120I DUAL BSDS DATA SETS HAVEUNEQUAL TIMESTAMPS, BSDS1SYSTEM=timestamp,UTILITY=timestamp, BSDS2SYSTEM=timestamp,UTILITY=timestamp

ExplanationWhen the log manager was initialized, the timestampsof the dual bootstrap data sets (BSDS) did not agree.The timestamps from the system and from the changelog inventory (DSNJU003) utility are shown for eachBSDS. The timestamps have the format yy.dddhh:mm:ss.th:

yyTwo-digit indicator for the year.

dddThree-digit indicator for the day of the year.

hh:mm:ss.thIndicator for the time of the day.

System actionDb2 attempts to re-synchronize the BSDS data sets torestore dual BSDS mode. If re-synchronization issuccessful, Db2 restart continues.

Operator responseIf restart fails, notify the system programmer.



System programmer responseIf restart fails, run the print log map (DSNJU004) utilityagainst each BSDS. From the output, determine whichdata set is obsolete, delete it, define a replacement forit, and copy the remaining BSDS to the replacement.

If output from the print log map (DSNJU004) utility forboth data sets is similar, delete the data set with theoldest timestamp, and copy the data set with the mostrecent timestamp.

Related referenceDSNJU003 (change log inventory) (Db2 Utilities)DSNJU004 (print log map) (Db2 Utilities)

DSNJ121I LOG MANAGER ENCOUNTERED ANERROR READING THE JFCB.DDNAME=nnnnnnnn

ExplanationDuring log manager initialization (if dual BSDS datasets are specified), the job file control block (JFCB) inMVS is read to obtain the data set names associatedwith DDNAME BSDS1 and BSDS2. This error is causedby a missing DD statement.

System actionDb2 is terminated.


System programmer responseEnsure that a DD statement exists in the Db2 startupprocedure for DDNAME BSDS1. If dual BSDS data setsare used, ensure that a DD statement also exists in theDb2 startup procedure for DDNAME BSDS2.

DSNJ122I DUAL BSDS DATA SETS ARE OUTOF SYNCHRONIZATION

ExplanationDuring log manager initialization or stand-alone utilityinitialization, the dual BSDS data sets were found todiffer in content in one of the following ways:

• A record that exists in both BSDSs is not identical.(This comparison accounts for some minordifferences.)

• A record exists in one BSDS and not in the other.• A required record is missing from one BSDS copy.

The print log map (DSNJU004) utility does not print allof the information in the BSDS. Therefore, the output

from DSNJU004 might be identical for two BSDSs, butthe BSDSs might still be different.

Example scenarios that might cause this probleminclude the following situations:

• The change log inventory (DSNJU003) utility wasused to alter one copy of a BSDS and not the other.

• Db2 was forced into single-BSDS mode due to an I/Oerror, and the stopped BSDS copy was not recovered.

System actionDb2 startup is terminated if the problem is detectedduring log manager initialization. If the problem isdetected by a stand-alone utility, the utility terminateswith return code 4.


System programmer responseIf the message was issued by Db2 initialization, runDSNJU004 against each BSDS to determine which ismore current. Delete the outdated copy, define areplacement for the deleted data set, and copy theremaining BSDS to the replacement by using IDCAMSREPRO.

If the message was issued by the DSNJCNVT utility,you can follow the same procedure as if the messagewas issued by Db2 initialization. Alternatively,DSNJCNVT can be run with the SYSUT2 DD statementomitted and a SYSUT1 DD statement that specifies thecorrect BSDS copy. The converted BSDS is written tothe SYSUT3 data set and, if provided, the SYSUT4 dataset.

Related referenceDSNJU004 (print log map) (Db2 Utilities)DSNJCNVT (Db2 Utilities)Related informationREPRO command (DFSMS Access MethodServices for Catalogs)

DSNJ123I CHANGE LOG INVENTORYFAILURE DETECTED

ExplanationDuring log manager initialization, the BSDS data setwas found to have been incompletely processed by thechange log inventory (DSNJU003) utility.







http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idai200/repro.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idai200/repro.htm

System programmer responseRun the print log map (DSNJU004) utility to determinewhat operation against the BSDS did not complete.Run the change log inventory (DSNJU003) utilityagainst the BSDS(s) to allow any unfinished processingto be completed.

DSNJ124I OFFLOAD OF ACTIVE LOGSUSPENDED FROM RBA xxxxxx TORBA xxxxxx DUE TO I/O ERROR

ExplanationDuring offload, an unrecoverable I/O error wasencountered on an active log data set. The data setexperiencing the error is marked unusable, and nofurther logging is done to that data set.

System actionActive log data sets continue to be offloaded as theybecome full.

Operator responseNotify the system programmer to initiate recoveryactions.

System programmer responseComplete the following steps:

1. Recover the data manually from the data set.2. Copy it to an archive data set.3. Run the change log inventory (DSNJU003) utility to

make the new archive data set available to the Db2subsystem.

4. Remove the error-prone active log data set fromDb2 by using the change log inventory utility.

DSNJ125I ERROR DUMPING BSDS, OFFLOADCONTINUING WITHOUTPRODUCING THE BSDS DUMP

ExplanationAn error occurred while dumping the bootstrap dataset (BSDS) during the offload process. The data set isnot produced, but the offload process continues. Thevolume containing the offloaded data set does notcontain a BSDS for recovery use.

System actionThe system continues the offload process withoutproducing a dump of the bootstrap data set.

DSNJ126I BSDS ERROR FORCED SINGLEBSDS MODE

ExplanationThe log manager encountered an I/O error or a VSAMlogical error on a bootstrap data set. This message ispreceded by message DSNJ107I or DSNJ108I.

System actionThe log manager enters single BSDS mode using theremaining BSDS.



System programmer responseExecute an offline access method services job torename the error BSDS and define a new BSDS withthe same name. Then enter the log manager -RECOVER BSDS command to reestablish dual BSDSmode.

DSNJ127I SYSTEM TIMESTAMP FORBSDS=timestamp

ExplanationWhen the log manager is initialized, the systemtimestamp for the bootstrap data sets (BSDS) isdisplayed. The timestamp has the format yy.dddhh:mm:ss.th:

yyTwo-digit indicator for the year.

dddThree-digit indicator for the day of the year.

hh:mm:ss.thIndicator for the time of the day.

This time stamp should be close to the last time atwhich this subsystem was stopped. If it not, then itmight indicate that a restart is being attempted withthe wrong BSDS.

System actionDb2 startup continues.


Operator responseIf the time displayed is not close to the time when thissubsystem was last stopped, contact the systemprogrammer.

System programmer responseIf you cannot explain the apparent time discrepancy,cancel the subsystem. From the startup procedure forthe subsystem services address space, determine thedata set names of the bootstrap data sets and run theprint log map (DSNJU004) utility. Check whether theactive and archive log data sets all belong to thissubsystem. If not, then change the startup procedurefor the subsystem services address space to use thecorrect bootstrap data sets.

Related referenceDSNJU004 (print log map) (Db2 Utilities)

DSNJ128I LOG OFFLOAD TASK FAILED FORACTIVE LOG nnnnn

ExplanationThe offload task abended while attempting to offloadthe relative byte address (RBA) range in active log dataset 'nnnnn'.

System actionThe offload task terminates and the archive data setsallocated to the offload task are deallocated anddeleted. The status of the active log data sets involvedin the failed offload processing remains set to 'notreusable'.

The log offload task will be re-initiated by one ofseveral events. The most common are:

• All the available space in the current active log dataset has been used (normal case).

• A DSNJ110E message is issued.• The database system services address space

(ssnmMSTR) is started, but data in the active log hasnot been archived.

• An I/O error occurs on the active log, which will forcethe system to truncate and offload the active logdata set, and switch to a new active log data set.

Operator responseThis message is the result of an offload failure, and willbe preceded by one or more Db2 messages (forexample, DSNJ073I) and/or MVS ABEND messages(for example, IEC030I, IEC031I, IEC032I). If Db2 isoperating with restricted active log resources (see

message DSNJ110E), quiesce the system to restrictlogging activity until the ABEND or the DSNJ110Econdition can be resolved. Notify the systemprogrammer.

System programmer responseThis message is the result of an offload failure, and willbe preceded by one or more Db2 messages (forexample, DSNJ073I) and/or MVS ABEND messages(for example, IEC030I, IEC031I IEC032I). Investigateand correct the cause of the ABEND before the offloadis attempted again by Db2.

Problem determinationThis message is the result of an offload ABEND andwill be preceded by one or more Db2 messages and/orMVS ABEND messages. See the documentation for theassociated Db2 and/or MVS messages to formulate acourse of corrective action. Use the print log map(DSNJU004) utility to print the BSDS (both copies ifrunning in dual mode), and then use the DSNJU004output to determine the current status of the activeand archive log data sets.

This message can be generated for a variety ofreasons. However, the most likely are:

• Archive log data set allocation errors. Refer to thetext for message DSNJ103I for corrective action.

• The size of the archive log data set is too small tocontain the active log data set(s) during offloadprocessing. All secondary space allocations havebeen used. This condition is normally accompaniedby MVS ABEND message IEC030I.

• All available space on the DASD volume(s) to whichthe archive data set is being written has beenexhausted. This condition is normally accompaniedby MVS ABEND message IEC032I.

• The primary space allocation for the archive log dataset (as specified in subsystem parameters) is toolarge to allocate to any available online DASD device.This condition is normally accompanied by MVSABEND message IEC032I.

DSNJ129I END OF log-rba eol-rba X COULDNOT BE FOUND IN ANY ACTIVELOG DATA SET HIGHEST RBAFOUND WAS hi-rba X

ExplanationThe log manager has been requested to find 'eol-rba',the log record which has been recorded in thebootstrap data set (BSDS) as the highest RBA written.This RBA cannot be found in any active log data set.



The highest RBA which could be found in any activedata set was 'hi-rba'.

System actionDb2 startup processing is terminated.


System programmer responseMost likely, the active log data set containing therequested RBA has been deleted from the BSDS by thechange log inventory (DSNJU003) utility. If the dataset has not been reused, run DSNJU003 to add thisdata set back into the BSDS. Restart Db2.

If the data set is not available, a conditional restartmust be performed to either truncate the log prior tothe RBA value of the missing data set, or to cold startat a higher RBA value. If you suspect an error in Db2,you might need to report the problem. For informationabout identifying and reporting the problem, seeCollecting diagnostic data (Collecting data). for moreinformation.

DSNJ130I ICF CATALOG NAME IN BSDSDOES NOT AGREE WITHDSNZPARM. BSDS CATALOGNAME=name, DSNZPARMCATALOG NAME=name

ExplanationThe ICF catalog name defined in DSNZPARM does notagree with the name contained in the bootstrap dataset (BSDS).

System actionDb2 startup is abended.

Operator responseIf you attempt to start the Db2 subsystem, you willreceive this same message and abnormal terminationwill result until the problem is resolved.

System programmer responseChange the ICF catalog name in the BSDS to agreewith the name defined in DSNZPARM during Db2initialization. To change the ICF catalog name in theBSDS, use the BSDS change log inventory (DSNJU003)utility with the NEWCAT control statement.


Problem determinationDuring log manager initialization, the ICF catalog namedefined in DSNZPARM is compared to the catalogname in the BSDS to ensure that the catalog nameused by the log manager during Db2 processing iscorrect. These names were found not to be the same.

DSNJ131I csect-name DUAL BSDS MODERESTORED FROM BSDSn

ExplanationDual BSDS mode has been restored using BSDS copyn. This copy is the BSDS data set with the most recentsystem timestamp.


DSNJ132I csect-name ARCHIVE LOG READERROR DSNAME=data-set-name,diag-information

ExplanationAn I/O error occurred attempting to read from archivelog data set data-set-name. The value for diag-information contains a portion of the message textgenerated by the SYNADAF macro to describe theerror. The generated message text containsinformation such as jobname, stepname, unit address,device type, ddname, operation attempted, and errordescription.

System actionDb2 will attempt the read request on a secondary copyof the archive log, if it is available. If a secondary copyof the archive does not exist, or this error occurs onthe secondary copy of the archive log, the log readrequest fails with reason code 00D10329.


System programmer responseIf the archive log read request is satisfied by asecondary archive log data set, no immediateresponse is required. Otherwise, attempt to determinethe cause of the I/O error and recover the archive dataset as required. For example, if the archive log data set



has been reblocked by moving or copying the data set,or by an HSM recall, it could result in a 'wrong lengthrecord' error. Use IEBGENER, or an equivalentprogram, to restore the data set with the original DCBinformation.

DSNJ138I csect-name OFFLOAD COMPLETEFOR LOG TRUNCATION FROM ANARCHIVE LOG COMMAND,ENDRBA=xxxxxxxxxxxx

ExplanationThis message indicates that the offload of thetruncated active logs, resulting from an -ARCHIVE LOGcommand, has completed successfully. xxxxxxxxxxxxis the ENDRBA of the truncated active logs and thenewly created archive log data sets.

DSNJ139I LOG OFFLOAD TASK ENDED

ExplanationProcessing of the active log offload ended.

System actionThis message is written to the MVS console.

Operator responseThis message does not guarantee that the offloadcompleted without errors. Check the console log andtask messages to review the execution of the offloadtask to determine whether any abnormal eventsoccurred during the offload.

DSNJ140I csect-name INVALID BSDSRELEASE LEVEL ACTIVE=xxxxxxARCHIVE=yyyyyy DSN=zzzzzz

ExplanationAt initialization time Db2 detected that the BSDS logrecords are not at the proper release level for thisrelease of Db2. 'xxxxxx' contains the release level forthe ACTIVE log records and 'yyyyyy' contains therelease level for the ARCHIVE log records. 'zzzzzz'contains the data set name for the BSDS encounteringthe error.

System actionDb2 startup will be terminated.

Operator responseNotify the system programmer so operatingprocedures can be changed.

System programmer responseRun the appropriate conversion program (DSNJMIG0or DSNJFAL0) to convert the BSDS data set to acompatible release level.

DSNJ150E LOG CAPTURE EXIT ABEND, EXITDEACTIVATED

ExplanationAn abnormal program interrupt was detected whileexecuting in the installation-supplied log capture exitcode (i.e. entry point DSNJW117 in load moduleDSNJL004). As a result of the abend, the log captureexit will no longer be active; log data will no longer beavailable for Exit capture/processing.

This message can only occur when an installation-supplied log capture exit (entry DSNJW117) is activefor this instance of Db2.

System actionThe log capture exit (entry point DSNJW117) isterminated. No further calls will be attempted for thisDb2 instance. A full dump is provided for diagnosticpurposes.



System programmer responseDetermine the cause of the DSNJL004 load module(DSNJW117 entry point) abend and take correctiveaction.

Attention: A correctly-functioning copy of load moduleDSNJL004/entry DSNJW117 must be available inorder to start Db2. If the problem which caused theabove abend cannot be corrected, ensure that thedefault DSNJW117 entry (load module DSNJL004 -supplied with the Db2 release) is available during thenext Db2 subsystem start.

User responseSee “System Programmer Response” below.

DSNJ151I csect-name IN READING log-typelog-value, A NONZERO REASONCODE WAS RETURNED.CONNECTION-ID=connection-id,CORRELATION-ID=correlation-id,


REASON-CODE=reason-code,MEMBER-ID=member-id

ExplanationDb2 could not successfully complete the read of thislog-value and log-type (RBA or LRSN) due to reasoncode 'ccc'. The member-id contains the ID of the datasharing member whose logs were being requested atthe time of the failure or zero if data sharing is notactive. The user or application that encountered theerror is identified by the connection and correlation ID.Messages that have the same connection ID andcorrelation ID relate to the same application.Correlation IDs beginning with '0nn', where nn is anumber from 01 to 28, identify system agents.

System actionDb2 attempts to recover from the error.

System programmer responseIf Db2 was able to recover from the error andsuccessfully complete the application, no furtheraction is required. If the application abnormallyterminated or Db2 could not recover successfully, thismessage is followed by one or more messages. Referto the information in this message and the subsequentmessages to determine the appropriate correctiveaction.

Related conceptsRecovering from BSDS or log failures duringrestart (Db2 Administration Guide)Related referenceDSN1LOGP (Db2 Utilities)Related informationRecovering from active log failures (Db2Administration Guide)Recovering from archive log failures (Db2Administration Guide)

DSNJ152I csect-name ERROR ENCOUNTEREDWHEN ATTEMPTING TO BUILDARCHIVE LOG VOLUME LIST.CONNECTION-ID=collection-id,CORRELATION-ID=correlation-id,REASON-CODE=reason-code

ExplanationAn error occurred while attempting to create theArchive Log Volumes report. An RBA range could notbe successfully mapped into one or more archive datasets due to reason code 'ccc'. The user or applicationthat encountered the error is identified by the

connection and correlation ID. This message might bepreceded by one or more related error messages.Messages that have the same connection ID andcorrelation ID relate to the same user. Correlation IDsbeginning with '0nn', where 'nn' is a number from 01 to28, identify system agents.

This failure could be caused by one or more missingarchive log data sets, or a system error (for example,an I/O error reading BSDS).

The Archive Log Volumes report (see messageDSNJ330I) is not produced. In addition, nopremounting of tapes is possible.

System actionThe user or application continues execution. Thephysical read process for the user or applicationcontinues until the job completes normally orterminates abnormally. The job can terminateabnormally if the error is encountered again when thedata set is physically required for the read process.

System programmer responseIf the user or application completes successfully, nofurther action is necessary. If the user or applicationdoes not complete successfully, refer to the messagesrelated to the actual failure to determine theappropriate corrective actions.

Related conceptsRecovering from BSDS or log failures duringrestart (Db2 Administration Guide)Related referenceDSN1LOGP (Db2 Utilities)Related informationRecovering from active log failures (Db2Administration Guide)Recovering from archive log failures (Db2Administration Guide)DSNJ330IARCHIVE LOG VOLUMES REQUIRED FORCONNECTION ID conn-id CORRELATION IDcorr-id

DSNJ153E csect-name CRITICAL LOG READERROR CONNECTION-ID =connection-id CORRELATION-ID =correlation-id LUWID = logical-unit-of-work-id=token REASON-CODE =reason-code




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_dsn1logp.html







https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_dsn1logp.html





ExplanationWhile processing a Db2 must-complete function, Db2encountered an error during an attempt to access therequired log data sets.

CONNECTION-ID, CORRELATION-ID, and LUWIDtogether identify the thread associated with therequest. token is a unique token number associatedwith the LUWID. reason-code identifies the mostrecent log-read failure.

System actionThe DSNJ154I message requests to retry the log-readrequest, and immediately follows this error message.Db2 will wait for a reply to message DSNJ154I beforeretrying the failed log-read request, or beforeabending.


System programmer responseReview the description of the reason-code associatedwith the log-read failure. Examine the system consolelog for additional messages regarding the log- readerror. Correct the cause of the error, if possible, andreply 'Y' to the DSNJ154I message in order to retry thelog-read request. If it is not possible to correct theproblem causing the log-read errors, and the failing logread request is the result of a thread rollback or -RECOVER POSTPONED command, consider cancelingthe log read request with the -CANCEL THREADNOBACKOUT or -RECOVER POSTPONED CANCELcommand. If canceling the log read request is not anoption, quiesce the work on the Db2 system beforereplying 'N' to the DSNJ154I message in preparationfor Db2 termination.

Related reference-CANCEL THREAD (Db2) (Db2 Commands)-RECOVER POSTPONED (Db2) (Db2 Commands)Related informationDSNJ154Icsect-name REPLY Y TO RETRY LOG READREQUEST, N TO ABEND

DSNJ154I csect-name REPLY Y TO RETRYLOG READ REQUEST, N TO ABEND

ExplanationWhile processing a Db2 must-complete function, Db2encountered an error during an attempt to access therequired log data sets.

System actionThe DSNJ153E message identifies the critical log-readerror, and immediately precedes this message. Db2will wait for the operator's reply to proceed with thelog-read request.

Operator responseNotify the system programmer. When actions havebeen taken to correct the cause of the log-read errors,reply 'Y' to request a retry of the failing log-readrequest. A reply of 'N' will fail the log-read request andthe task will abend. Db2 then terminates.

System programmer responseReview the description of the reason-code associatedwith the log-read failure, and examine the systemconsole log for additional messages regarding the log-read error. Correct the cause of the error, if possible,and reply 'Y' to the DSNJ154I message to retry thelog-read request. If it is not possible to correct theproblem causing the log-read errors, quiesce the workon the Db2 system before replying 'N' to the DSNJ154Imessage in preparation for Db2 termination.

DSNJ156I INVALID BSDS CONVERSION,DSN=dataset-name

ExplanationDuring initialization time, Db2 detected an invalidBSDS. An invalid BSDS can result from a failure duringa prior attempt to run a conversion program.

dataset-nameThe data set name for the BSDS encountering theerror.

System actionDb2 startup terminates.

System programmer responseThe procedure for running the conversion programincludes making a copy of the BSDS before conversion.Restore the BSDS to the original pre-conversion copy,and try the conversion again. After the conversion issuccessful, restart Db2.

Related referenceDSNJCNVB (Db2 Utilities)DSNJCNVT (Db2 Utilities)

DSNJ157I BSDS HAS NOT BEEN CONVERTED,DSN=ds-name



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_recoverpostponed.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_dsnjcnvb.html


ExplanationDuring restart, Db2 detected a BSDS that was neithercreated in nor converted to the format that allows10,000 archive logs.

ds-nameThe data set name of the BSDS that encounteredthe error.


System programmer responseRun the DSNJCNVB program and restart Db2.

Related conceptsThe extended 10-byte RBA and LRSN in Db2 11(Db2 for z/OS What's New?)Related tasksMigration step 17: Start Db2 11 (Db2Installation and Migration)Related referenceDSNJCNVT (Db2 Utilities)DSNJCNVB (Db2 Utilities)

DSNJ158I csect-name ACTIVE LOG DATA SETDSN=dsname IS GREATER THAN 4GB IN SIZE

ExplanationAn active log data set has a size of greater than 4 GB,but new function is not activated in Db2 Db2 12.Before function level 500 is activated in Db2 12, themaximum supported active log data set size is 4 GB.

dsnameThe name of the active log data set that caused theerror.

System actionThe system action depends on when the Db2 databasemanager detects that the data set size is too big:

• During processing of the -SET LOG NEWLOGcommand:

The -SET LOG NEWLOG command fails.• During Db2 startup:

Db2 abnormally terminates with reason code00E80084.

System programmer responseThe system programmer response depends on whenthe Db2 database manager detects that the data setsize is too large:


1. Reallocate the data set with a size of less than 4GB.

2. Issue -SET LOG NEWLOG• During Db2 startup:


– Reallocate the data set with a size of less than4 GB.

Tip: If the error occurs during migration to Db212, take this action. When you run thepremigration job DSNTIJPM, report 24identifies active log data sets with a sizegreater than 4 GB.

– Run the DSNJU003 utility with the DELETEdsname control statement to delete the activelog data set from the bootstrap data set.

2. Restart Db2.

Related tasksRun premigration queries (DSNTIJPM) (Db2Installation and Migration)Related reference-SET LOG (Db2) (Db2 Commands)DSNJU003 (change log inventory) (Db2 Utilities)

DSNJ159I csect-name ACTIVE LOG DATA SETDSN=dsname IS GREATER THAN768 GB IN SIZE

ExplanationAn active log data set has a size of greater than themaximum supported size, 768 GB.

dsnameThe name of the active log data set that caused theerror.

System actionThe system action depends on when the Db2 databasemanager detects that the data set size is too big:


The -SET LOG NEWLOG command fails.• During Db2 startup:




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_startdb2migr.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_startdb2migr.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntijpm.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntijpm.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_setlog.html


Db2 abnormally terminates with reason code00E80084.

System programmer responseThe system programmer response depends on whenthe Db2 database manager detects that the data setsize is too big:


1. Reallocate the data set with a size of less than768 GB.

2. Issue -SET LOG NEWLOG• During Db2 startup:


– Reallocate the data set with a size of less thanor equal to 768 GB.

– Run the DSNJU003 utility with the DELETEdsname control statement to delete the activelog data set from the bootstrap data set.

2. Restart Db2.

Related reference-SET LOG (Db2) (Db2 Commands)DSNJU003 (change log inventory) (Db2 Utilities)

DSNJ200I csect-name utility-name UTILITYPROCESSING COMPLETEDSUCCESSFULLY member-name

ExplanationExecution of a utility completed successfully.


utility-nameThe name of the utility.

member-nameIn a data sharing environment, the name of thedata sharing member on which the utility ran. In anon-data sharing environment, the member nameis set to UNKNOWN.

System actionDb2 writes this message to the SYSPRINT data set, notto a console.

DSNJ201I csect-name xxxxxxxx UTILITYPROCESSING WASUNSUCCESSFUL

ExplanationThe control section 'csect-name' was unable tosuccessfully complete processing of 'xxxxxxxx' utility.

System actionThe current utility is terminated. Db2 writes thismessage to the SYSPRINT data set, not to a console.

User responseReview other messages produced by the utility todetermine the appropriate action to be taken.

DSNJ202I csect-name INSUFFICIENTVIRTUAL STORAGE AVAILABLE TOCONTINUE WITH UTILITY

ExplanationA GETMAIN macro instruction has failed, becausevirtual storage is unavailable for the job-step.

System actionThe current utility is terminated. This message iswritten to the SYSPRINT data set, not to a console.

User responseRerun the utility after providing a larger virtual storageallocation for the job-step.

DSNJ203I xxxxxxxx OPERATION IS INVALID

ExplanationThe user entered a utility control statement operationof xxxxxxxx that is invalid.

The DSNJU003 utility fails if the DSNTIJGF job is usedas part of disabling data sharing on a Db2 11 new-function mode BSDS that was not converted by theDSNJCNVT conversion utility.


User responseCorrect the control statement, and rerun the utility.

If disabling data sharing is required, convert the BSDSwith the DSNJCNVT conversion utility before rerunningthe utility.

DSNJ204I xxxxxxxx PARAMETER IS INVALID




ExplanationThe user specified a utility control statementparameter of 'xxxxxxxx' that is invalid.



DSNJ205I xxxxxxxx PARAMETER HAS NOARGUMENT

Explanation'xxxxxxxx' contains the name of a parameter thatrequires an argument.


User responseSpecify an argument for the identified parameter andthen rerun the utility.

DSNJ206I xxxxxxxx PARAMETER REQUIRESNO ARGUMENT

Explanation'xxxxxxxx' contains the name of the parameter thathas been incorrectly followed by an = symbol.



DSNJ207I csect-name PARAMETERSINCONSISTENT WITH SPECIFIEDOPERATION

ExplanationThe user has specified utility control statementparameters that are inconsistent with the specifiedutility operation.



DSNJ208E csect name MEMBER member nameWAS NOT FOUND IN THE BSDSSPECIFIED IN THE GROUP DDSTATEMENT.

ExplanationYou are running the print log map (DSNJU004) utility.No member record exists for this member in thebootstrap data set (BSDS) specified in the GROUP DDstatement.

System actionThe log map for this member is not printed. If therecords for other members are requested and arefound in the BSDS specified in the GROUP DDstatement, they are printed.

User responseUse the DISPLAY GROUP command to verify that themember name is a valid name and that the memberhas successfully joined the group. Also verify that theBSDS specified in the GROUP DD statement is correct.If the member name and the BSDS name are correct,then the most likely causes of this message are:

• The 'missing member' never joined the groupbecause it was never started.

• The member whose BSDS you specified in theGROUP DD statement was down when the missingmember joined the group and has not beenrestarted.

To gather the information from the missing member,you can rerun the utility, using the BSDS DDNAMEoption to point to the missing member's BSDS. Toavoid this problem in the future, make sure the BSDSnamed in the GROUP statement is from a recentlystarted member.

DSNJ209I ENDRBA VALUE MUST BEGREATER THAN STARTRBA VALUE

ExplanationThe 'STARTRBA' and 'ENDRBA' parameters specify anRBA range. Hence, the ENDRBA value must be greaterthan the STARTRBA value.




DSNJ210I OLD ICF CATALOGNAME=oldname, NEW CATALOGNAME=newname

ExplanationChange log inventory (DSNJU003) utility processing forthe NEWCAT control statement has completedsuccessfully.oldname

Either:

• The name of the prior ICF catalog or• 'NULL' if no prior name existed.

newnameThe name of the ICF catalog defined by theVSAMCAT keyword.

DSNJ211I UNEXPECTED END OF DATA ONSYSIN DATA SET

ExplanationAdditional control statements were expected butcould not be found.


User responseCorrect the control statement(s), and rerun the utility.

DSNJ212I csect-name ERROR RETURNEDFROM BSDS READ, RPLERRCD=yy,DDNAME=xxxxxxxx

ExplanationA VSAM GET was issued that resulted in a nonzeroreturn code. 'yy' contains the error code returned byVSAM. 'xxxxxxxx' contains the ddname of the BSDSencountering the error.


User responseThe action taken is dictated by the return code. TheBSDS may have to be recovered by use of a backupcopy.

DSNJ213I csect-name ERROR RETURNEDFROM BSDS WRITE,RPLERRCD=vsam-code,DDNAME=dd-name

ExplanationA VSAM PUT or ERASE macro was issued, and itreturned a nonzero return code.


vsam-codeThe return code that was returned by VSAM.

dd-nameThe data definition name of the BSDS thatencountered the error.

System actionThe current utility is terminated. Message DSNJ213I iswritten to the SYSPRINT data set. The message is notwritten to console.

User responseUse the VSAM return code information to resolve theproblem. The BSDS might need to be recovered from abackup copy.

Related referenceVSAM Macro Return and Reason Codes (DFSMSMacro Instructions for Data Sets)

DSNJ214I SPECIFIED DSNAME ALREADYEXISTS IN BSDS,DDNAME=xxxxxxxx

ExplanationThe user attempted a NEWLOG operation with a dataset name that already exists in the BSDS. An entry isnever made in a BSDS if the specified DSNAMEcurrently exists in either the active or archive recordsof that BSDS. 'xxxxxxxx' contains the ddname of thesubject BSDS.



http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/x1a.htm


User responseEither correct the control statement and rerun theutility, or delete the existing DSNAME from the BSDSand rerun the utility.

DSNJ215I csect-name SVC 99 INFORMATIONREQUEST FOR DD NAME 'ddname'FAILED. RC= rc, RSN= rsncd, ANDINFO CODE infocode.

ExplanationThe DSNJU004 (print log map) utility requestedinformation from the z/OS Dynamic Allocation facilityabout the indicated DD name, but the system wasunable to provide the information.


ddnameThe DD name.

rcThe return code from the z/OS DYNALLOC (SVC 99)service.

rsncdThe reason code from the z/OS DYNALLOC (SVC99) service.

infocodeThe information code from the z/OS DYNALLOC(SVC 99) service.

System actionIf the information request was for the SYSIN DDstatement, DSNJU004 assumes that the controlstatement was not provided. DSNJU004 attempts tocontinue the request by using the SYSUT1 DDstatement to locate the BSDS to be mapped.

If the information request was for the DD name of aBSDS, the attempts to get information about BSDSdata sets are stopped. If information about any BSDSdata sets was previously acquired, the maps of thoseBSDS data sets are printed. Otherwise, the utilityterminates.

System programmer responseSee the reason code for DYNALLOC to determine theaction to take.

Problem determinationIf you suspect an error in Db2, you might need toreport the problem. For information about identifying



• SYSABEND, SYSUDUMP, or SYSMDUMP output.• SYSPRINT output, including JCL, for the application

program or batch job, and system messages thatwere issued. Make sure that MSGLEVEL=(1,1) on theJOB statement so that all diagnostic information issent to SYSPRINT.


DSNJ216I NO SPACE IN BSDS FORADDITIONAL ACTIVE LOGENTRIES, DDNAME=xxxxxxxx

ExplanationThe maximum number of active log data sets is fixed.No further entries can be inserted after the maximumhas been reached. xxxxxxxx contains the ddname ofthe subject BSDS.


User responseRun the print log map utility to determine the currentstatus of the BSDS. Subsequent actions can then beformulated, depending upon the status of the BSDS.

DSNJ217I SPECIFIED DSNAME DOES NOTEXIST IN BSDS,DDNAME=xxxxxxxx

ExplanationThe DELETE operation specifies a DSNAME that cannotbe found in the BSDS. 'xxxxxxxx' contains the ddnameof the subject BSDS.









DSNJ218I SPECIFIED VOLUME DOES NOTEXIST IN BSDS,DDNAME=xxxxxxxx

ExplanationThe DELETE operation specifies a COPY1VOL orCOPY2VOL argument that cannot be found in theBSDS. 'xxxxxxxx' contains the ddname of the subjectBSDS.



DSNJ219I csect-name OPEN ERROR,DDNAME=xxxxxxxx

ExplanationAn error occurred when the CSECT 'csect-name' triedto open a data set named 'xxxxxxxx'.

This error can be caused by a number of differentconditions. The most probable conditions are:

1. The ddname of the SYSPRINT, SYSIN, or SYSUT1data set was not specified in the user's job controllanguage (JCL).

2. The Db2 subsystem is currently executing.3. The bootstrap data set (BSDS) was allocated by

another job with a disposition (DISP) that conflictswith the DISP specified in the user's JCL.

4. The data set associated with 'xxxxxxxx' is alreadyopen, possibly due to an earlier system abend.

5. The user is not authorized to access the data setassociated with 'xxxxxxxx'

6. Insufficient virtual storage is available to performthe OPEN command.

7. The catalog indicates that the data set associatedwith 'xxxxxxxx' has an invalid physical record size.

System actionThe current utility is terminated.

Db2 writes this message to the SYSPRINT data set, notto a console.

User responseThe user's action depends on the condition thatcaused the OPEN error. The following is a list of

appropriate actions corresponding to the conditionslisted in the explanation:

1. Provide the missing DD statements, and then rerunthe utility.

2. Wait until the Db2 subsystem is inactive beforerunning the utility again because the log utilitycannot execute while the Db2 subsystem is active.

3. Correct the disposition conflict and then rerun theutility.

4. Submit an access method services (IDCAMS)VERIFY job against the data set associated with'xxxxxxxx'. Rerun the log utility job.

5. In the case of an authorization failure, a separatemessage is usually generated from theauthorization facility (RACF, for example).Investigate the authorization messages and obtainthe proper authorization before running the utilityagain.

6. Insufficient virtual storage is usually accompaniedby a separate error from the MVS operating system.Increase the REGION size on the JCL job step andrerun the utility.

7. Contact the system programmer.

Related tasksInvoking stand-alone utilities (Db2 Utilities)

DSNJ220I BSDS IN CREATE MODE. NO DATATO MAP, DDNAME=nnnnnnnn

ExplanationA utility found the BSDS to be in create mode, meaningit contains no data. nnnnnnnn contains the ddname ofthe BSDS data set.


User responseEnsure that the BSDS data set name specified as inputto the utility is correct.

DSNJ221I PREVIOUS ERROR CAUSEDxxxxxxxx OPERATION TO BEBYPASSED

ExplanationDb2 encountered errors while processing a utility.These errors subsequently caused 'xxxxxxxx' to bebypassed.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_invokestandaloneutl.html

This message is a warning only and is displayed aftermessages that specify the error or errors that causedthe utility operation to abend. Note that the error orerrors may not be associated with the current'xxxxxxxx' operation; rather, under log utilityprocessing, a significant error in any operation causesthe control statements for this and any subsequentoperations to be checked for syntax only. BSDSupdates do not occur for any operation specified in thismessage.

System actionThe log utility continues to process. However, for thisand all subsequent operations, the bootstrap data set(BSDS) is not updated and the utility only checks thesyntax of the control statements.


User responseConsult the previous messages and correct any errorsthat caused this message to be generated. Resubmitthe log utility job for all operations that have beenbypassed.

DSNJ222I INVALID SPECIFICATION OF xxxxPARAMETER ARGUMENT

ExplanationYou specified the parameter 'xxxx'. This parameter isnot valid for the argument.


User responseCorrect the parameter argument on the controlstatement, and rerun the utility.

DSNJ223I xxxx PARAMETER ARGUMENTEXCEEDS MAXIMUM ALLOWABLELENGTH

ExplanationThe argument value of the parameter named 'xxxx'exceeds the maximum length allowed.


User responseCorrect the parameter argument on the controlstatement, and rerun the utility.

DSNJ224I xxxx PARAMETER APPEARS TOOOFTEN

ExplanationThe parameter named 'xxxx' was specified more thanonce on the same control statement.


User responseRemove the redundant parameter, and rerun theutility.

DSNJ225I xxxx OPERATION COMPLETEDSUCCESSFULLY

ExplanationThe change log inventory (DSNJU003) utility operationnamed 'xxxx' completed successfully.

System actionThis message is written to the SYSPRINT data set, notto a console.

DSNJ226I SPECIFIED VOLUME ALREADYEXISTS IN BSDS,DDNAME=xxxxxxx

ExplanationThe specified volume currently exists in the archive logrecords of the BSDS. 'xxxxxxxx' specifies the ddnameof the subject BSDS.


User responseEither correct the parameter argument on the controlstatement, or delete the specified volume and rerunthe utility.

DSNJ227I NO SPACE AVAILABLE IN BSDSFOR ADDITIONAL ARCHIVE


VOLUME ENTRIES,DDNAME=xxxxxxxx

ExplanationThe maximum number of archive volumes has beenexceeded, and no more space is available for volumeentries in the copy specified.

System actionThe current utility is terminated.

User responseDelete some of the archive entries in the specifiedcopy number, and rerun the utility.

DSNJ228I csect-name LOG DEALLOCATIONERROR DSNAME=dsname, ERRORSTATUS=eeeeiiii, SMS REASONCODE=ssssssss

ExplanationThe log manager encountered an error while trying todynamically deallocate the data set. Error status is theerror reason code returned by MVS dynamic allocation.

System actionLog manager processing continues.


System programmer responseThe error status portion of this message contains the2-byte error code (S99ERROR) followed by the 2-byteinformation code (S99INFO) from the SVC requestblock. If the S99ERROR code indicates an SMSdeallocation error (97XX), then 'ssssssss' containsadditional SMS reason code information obtained fromS99ERSN.

DSNJ229I csect-name OPEN FAILED FORSYSIN

ExplanationAn error occurred when the Db2 Print Log Map utilitytried to open the SYSIN data set.

Possible causes are:

1. The DD name of the SYSIN data set was notspecified in the user's job control language (JCL).

2. Insufficient virtual storage is available to performthe OPEN command.

3. The characteristics of the SYSIN data set aredifferent from those expected by the print log map(DSNJU004) utility.

System actionDSNJU004 attempts to continue processing withoutan input control statement. Db2 writes this message tothe SYSPRINT data set, not to the system console.

User responseTake one of the following actions based on the causeof the error.

1. Provide the missing DD statement and rerun theutility.

2. Insufficient virtual storage is usually accompaniedby a separate error message from the MVSoperating system. Increase the REGION size on theJCL job step and rerun the utility.

3. Check that the SYSIN data set is a fixed recordformat (blocked or unblocked) with an LRECL of 80.You might need to contact the system programmerfor help if this is a JES data set.

Related tasksInvoking stand-alone utilities (Db2 Utilities)Related referenceSyntax and options of the DSNJU004 controlstatement (Db2 Utilities)

DSNJ230I LOG OFFLOAD SUBCOMPONENTINITIALIZATION PROCESSINGFAILED

ExplanationDuring log manager initialization, the off-load functionwas unable to complete its initialization process.



System programmer responseOne or more error messages describing the specificerror preceded this message. Refer to the specificmessage(s) for error analysis and the appropriateactions to take.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_dsnju004syntax.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_dsnju004syntax.html

DSNJ231I LOG COMMAND INITIALIZATIONPROCESSING FAILED

ExplanationDuring log manager initialization, the log commandfunction was unable to complete its initializationprocess.


Operator responseThe rest of subsystem termination will direct theactions you should take.

System programmer responseOne or more error messages describing the specificerror preceded this message. Refer to the specificmessage(s) for error analysis and the appropriateaction to take.

This message will be of interest to the IBM supportcenter when the problem is described.

DSNJ232I OUTPUT DATA SET CONTROLINITIALIZATION PROCESSINGFAILED

ExplanationDuring log manager initialization, the output data setcontrol function was unable to complete itsinitialization process.


System programmer responseOne or more error messages describing the specificerror preceded this message. Refer to the specificmessage for error analysis and the appropriate actionto take.

This message will be of interest to the IBM supportcenter when the problem is described.

DSNJ233I ARCHIVE LOG READINITIALIZATION PROCESSINGFAILED

ExplanationDuring log manager initialization, the archive log readfunction was unable to complete its initializationprocess.




DSNJ234I ARCHIVE LOG COMMANDQUIESCE INITIALIZATIONPROCESSING FAILED

ExplanationDuring log manager initialization, the quiesce functionwhich supports the -ARCHIVE LOG MODE(QUIESCE)command processing was unable to complete itsinitialization process.




DSNJ235I OUTPUT BUFFER WRITERINITIALIZATION PROCESSINGFAILED

ExplanationDuring log manager initialization, the output bufferwriter function was unable to complete its initializationprocess.





DSNJ236I BOOTSTRAP ACCESSTERMINATION PROCESSINGFAILED

ExplanationDuring log manager termination, the bootstrap dataset access function was unable to complete itstermination process.

System actionLog manager shutdown continues to the next step.



DSNJ237I csect-name INVALID CONTROLSTATEMENT. THE FIRST WORDMUST BE 'MEMBER'.

ExplanationThe print log map (DSNJU004) utility read an invalidcontrol statement from the SYSIN data set.

System actionDSNJU004 ignores the control statement andattempts to continue processing by looking for aSYSUT1 DD statement to describe the BSDS that is tobe printed.

User responseCorrect or remove the control statement and rerun thejob.

Problem determinationIf you suspect an error in Db2, you might need toreport the problem. For information about identifyingand reporting the problem, see Collecting diagnosticdata (Collecting data).


• SYSPRINT output, including JCL, for the applicationprogram or batch job, and system messages thatwere issued. Make sure that MSGLEVEL=(1,1) on theJOB statement so that all diagnostic information issent to SYSPRINT.

Related referenceDSNJU004 (print log map) (Db2 Utilities)Sample DSNJU004 control statement (Db2Utilities)

DSNJ238I LOG OFFLOAD TERMINATIONPROCESSING FAILED

ExplanationDuring log manager termination, the offload functionwas unable to complete its termination process.



System programmer responseOne or more error messages describing the specificerror preceded this message. Refer to the specificmessages for error analysis and the appropriate actionto take.

DSNJ239I LOG COMMAND TERMINATIONPROCESSING FAILED

ExplanationDuring log manager termination, the log commandfunction was unable to complete its terminationprocess.






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_dsnju004samples.html




DSNJ240I OUTPUT DATA SET CONTROLTERMINATION PROCESSINGFAILED

ExplanationDuring log manager termination, the output data setcontrol function was unable to complete itstermination process.

System actionThe log manager shutdown continues to the next step.



DSNJ241I ARCHIVE LOG READTERMINATION PROCESSINGFAILED

ExplanationDuring log manager termination, the archive log readfunction was unable to complete its terminationprocess.



System programmer responseOne or more error messages describing the specificerror preceded this message. Refer to the specific

message(s) for error analysis and the appropriateaction to take.

DSNJ242I ARCHIVE LOG COMMANDQUIESCE TERMINATIONPROCESSING FAILED

ExplanationDuring log manager termination, the quiesce functionwhich supports the -ARCHIVE LOG MODE(QUIESCE)command processing was unable to complete itstermination process.




DSNJ243I OUTPUT BUFFER WRITERTERMINATION PROCESSINGFAILED

ExplanationDuring log manager termination, the output bufferwriter function was unable to complete its terminationprocess.




DSNJ244I LOG TERMINATION RECEIVEDRETURN CODE nnn FROMxxxxxxxx MACRO


ExplanationLog manager termination was passed a bad returncode from the named macro.

System actionLog manager termination processing continues.

Operator responseRecord the return code and macro-name, and notifythe system programmer.

System programmer responseThis message is associated with a failure in the namedmacro. If you suspect an error in Db2, you might needto report the problem. For information aboutidentifying and reporting the problem, see Collectingdiagnostic data (Collecting data).

DSNJ245I CONDITIONAL RESTART - LOGTRUNCATION AT xxx rrr. REPLY YTO CONTINUE, N TO CANCEL

ExplanationThe conditional restart control record in use indicatesthat the Db2 log should be truncated at the specifiedRBA or LRSN.xxx is replaced by either RBA or LRSN,and rrr is the value specified in the current record.

System actionIf Y, Db2 startup continues. If N, Db2 startup isterminated.

Operator responseReply N if the truncation is going to occur at anundesirable point. Notify system programmer. Reply Yto continue the restart.

System programmer responseRerun the change log inventory (DSNJU003) utility tomodify the conditional restart record.

DSNJ246I CONDITIONAL RESTART - COLDSTART AT RBA rrr. REPLY Y TOCONTINUE, N TO CANCEL

ExplanationThe conditional restart control record in use indicatesthat Db2 is to be restart and that logging is to begin atthe specified RBA.

System actionIf Y, Db2 startup continues. If N, Db2 startup isterminated.

Operator responseReply N if the truncation is going to occur at anundesirable point. Notify the system programmer.Reply Y to continue the cold start.

System programmer responseRerun the change log inventory (DSNJU003) utility tomodify the conditional restart record.

DSNJ247E csect-name I/O ERROR DURINGPROCESSING OF rrr RC = rc,REASON = reason

ExplanationThe I/O error occurred at record 'rrr'. 'rc' indicates thereturn code received from the I/O operation. 'reason'indicates the reason code received from the I/Ooperation.

If a return code '4' was received, this indicates that thelog manager detected a problem. If a return code '8'was received, this indicates a VSAM error.




For a return code of '4', if you suspect an error in Db2,you might need to report the problem. For informationabout identifying and reporting the problem, seeCollecting diagnostic data (Collecting data). For areturn code of '8', execute an offline access methodservices job to determine the cause of the VSAM error.

DSNJ248I ARCHIVE LOG READDEALLOCATION INITIALIZATIONPROCESSING FAILED







ExplanationDuring log initialization, the archive log readdeallocation process was unable to complete itsinitialization.



System programmer responseOne or more error messages describing the specificerror precede this message. Refer to these messagesfor error analysis and the appropriate action to take.

DSNJ249I ARCHIVE LOG READ SCHEDULERINITIALIZATION PROCESSINGFAILED

ExplanationDuring log initialization, the archive log readscheduling process was unable to complete itsinitialization.



System programmer responseOne or more error messages describing the specificerror precede this message. Refer to these messagesfor error analysis and the appropriate action to take.

DSNJ250E csect-name DATA SHARINGREQUIRES ALL ACTIVE LOG DATASETS TO BE DEFINED WITHSHAREOPTIONS(2 3) OR HIGHER.

ExplanationDb2 detected an active log data set defined with shareoptions that do not permit recovery operations in adata sharing environment. This message is followed bymessage DSNJ251E, which identifies the specificactive log data set.

All active log data sets for a Db2 data sharing membermust be defined with a minimum of SHAREOPTIONS(2

3) for successful Db2 initialization. See the descriptionof message DSNJ251E for more details.

System actionThe Db2 subsystem detecting this condition isterminated.

DSNJ251E csect-name DATA SET dsnameFAILS TO MEET THE MINIMUMREQUIRED SHAREOPTIONS FORDATA SHARING.

ExplanationThe share options defined for the data set named inthe message are too low to permit the data set toparticipate in a Db2 data sharing group. All active logdata sets must be defined with SHAREOPTIONS(2 3)or higher in order to participate in a data sharinggroup.

System actionThe Db2 subsystem detecting this error is terminated.

System programmer responseUsing IDCAMS LISTCAT or TSO LISTCAT, display theshare options of all of the active log data sets of all ofthe members in the data sharing group. For any activelog data set that is defined with less thanSHAREOPTIONS(2 3), use IDCAMS ALTER or TSOALTER to alter the data set definitions toSHAREOPTIONS(2 3) or higher.






• IDCAMS LISTCAT output that shows the attributes ofall active log data sets for the Db2 member thatfailed.

.




DSNJ252E csect-name CURRENT DATASHARING LRSN current-lrsn ISLESS THAN HIGH WRITTEN LRSNhigh-lrsn

ExplanationThe current log record sequence number (LRSN) is lessthan the high written LRSN in the log. This conditionindicates that the system time is now less than thetime that is recorded earlier in the Db2 log data sets.To ensure that log records and database updates areapplied in the correct order, Db2 data sharing requiresthat the LRSN always advances.csect-name


current-lrsnThe current log LRSN. This value is obtained fromthe system time-of-day (TOD) clock.

high-lrsnThe high written LRSN in the log.



System programmer responseMake sure that the system TOD clock was not set to anearlier date and time. If you are restarting Db2 on aremote Sysplex, make sure that the system TOD clockis not set to an earlier date and time than the primarySysplex.

DSNJ253I csect-name alias-port USE ISINVALID

ExplanationThe alias-port value has been used in an invalidmanner. The error could be due to one of the followingconditions:

• alias-port was specified after more than one alias-name parameter

• alias-port duplicates the port value for the PORT orRESPORT parameters which have been specifiedwith this update, or are already stored in the BSDS

System actionThe update of the BSDS will not be performed.

User responseRetry the BSDS update with unique alias-port values,which also do not match the values for the PORT orRESPORT parameters.

DSNJ254I xxxx NUMBER OF PARAMETERARGUMENTS EXCEED MAXIMUMVALUE

ExplanationThe number of arguments for the parameter namedxxxx exceed the maximum value allowed.

System actionThe current operation is terminated. This message iswritten to the SYSPRINT data set, but not written to aconsole.

User responseChange the number of parameter arguments on thecontrol statement, and rerun the utility.

DSNJ255I csect-name CONDITIONALRESTART ENDTIME OF end-timeWILL RESULT IN LOGTRUNCATION AT xxxxyyyyyyyyyyyy

ExplanationThe conditional restart control record in use indicatesthat the Db2 log should be truncated with ENDTIMEend-time. The ENDTIME value translates to truncationtype xxxx with value yyyyyyyyyyyy. This value is eitheran LRSN value (for data sharing) or a STCK (storeclock) value (for non-data sharing).

System actionStartup continues.

User responseReply Y to the DSNJ245I WTOR if this value is thecorrect log truncation value.

DSNJ256I csect-name CONDITIONALRESTART RECORD INDICATESSYSPITR RESTART WITH NO LOGTRUNCATION

ExplanationThe conditional restart control record in use indicatesthat Db2 will be restarted in system recover pending


mode without truncating the logs. No database updateactivity will be allowed, and Db2 will be in restrictedaccess mode.

System actionStartup continues.

Operator responseReply 'Y' to the DSNJ011I WTOR if this is correct.

DSNJ260I csect_name BSDS CONVERSIONFOR DDNAME=nnnnnnnnCOMPLETED SUCCESSFULLY

ExplanationThe BSDS conversion utility issues this message toindicate a successful conversion for the BSDS data setspecified by the nnnnnnnn DDNAME.


DSNJ261I csect_name BSDS CONVERSIONFOR DDNAME=nnnnnnnn WASNOT SUCCESSFUL

ExplanationThe BSDS conversion utility issues this message toindicate conversion was not successful for the BSDSdata set specified by the nnnnnnnn DDNAME.

System actionThe action taken depends on whether dual BSDS datasets are specified, and if so, which conversion failed.The DDNAME in the message indicates the failingBSDS data set.

If dual BSDS data sets are specified, the SYSUT1 dataset is converted first. If that conversion is successful,the SYSUT2 data set is then converted. A failure at thispoint does not affect the successful SYSUT1conversion.

If conversion fails for the SYSUT1 data set, processingis terminated at that point. In this case, any SYSUT2data set that was specified will not be converted.

User responseReview other messages produced by the utility todetermine the cause of the failure and the resultingaction to take.

DSNJ266I WARNING - BSDS UTILITYTIMESTAMP MISMATCHDETECTED. PROCESSINGTERMINATED.

ExplanationDb2 detected a mismatch in the timestamps for theSYSUT1 and SYSUT2 BSDS copies during execution ofa BSDS conversion utility. This mismatch indicates thepossibility that the dual BSDSs are out of sync.

System actionThe program terminates with no action taken.

System programmer responseRun the print log map utility (DSNJU004) against eachBSDS. From the output, determine which data set isobsolete, delete it, and define a replacement for it.Then copy the remaining data set into the replacementand try the utility again.

If output from the print log map utility for both datasets is similar, delete the data set with the oldesttimestamp, and copy the data set with the most recenttimestamp into the replacement.

Related referenceDSNJU004 (print log map) (Db2 Utilities)DSNJCNVB (Db2 Utilities)DSNJCNVT (Db2 Utilities)

DSNJ301I csect-name ERROR action ONLINEBOOTSTRAP DATA SET

ExplanationDuring command processing for the -RECOVER BSDScommand or the -ARCHIVE LOG command, an erroroccurred while performing an operation on thebootstrap data set (BSDS). The type of operation isspecified in the 'action' keyword in the message text:

• ACCESSING: Unable to OPEN the BSDS.• READING: Unable to read a required record from the

BSDS.• UPDATING: Unable to write a required record to the

BSDS.• RESTORING DUAL: The contents of the stable BSDS

was successfully copied to the replacement BSDS;however, the Db2 subsystem was unable tosuccessfully restore dual BSDS operation.





System actionIf this message was received during processing of the -RECOVER BSDS command, the Db2 subsystem willcontinue in single BSDS mode. If this message wasreceived during processing of the -ARCHIVE LOGcommand, the archive log history record in the BSDSwill not be updated to reflect the occurrence of an -ARCHIVE LOG command; logging and the offloadprocessing will continue.

Operator responseInform the system programmer of the type of errorthat occurred, and whether the error occurred whileprocessing a -RECOVER BSDS command or an -ARCHIVE LOG command.

System programmer responseIf this message was received during processing of the -RECOVER BSDS command, recovery action must beperformed on the bootstrap data set before reenteringthe command. If this message was received duringprocessing of the -ARCHIVE LOG command, no actionis necessary.

DSNJ302I ALLOCATION ERROR ONREPLACEMENT BSDS DSNAME=...ERROR STATUS=...

ExplanationThe RECOVER BSDS command encountered an errorwhile trying to dynamically allocate the specified dataset. DSNAME is the data set name. Error Status is theerror code and information code returned by MVSdynamic allocation.

System actionProcessing of the command is terminated. The systemcontinues in single BSDS mode.

Operator responseDetermine the cause of the error from the error statuscontained in the message, and correct the condition.Then reenter the -RECOVER BSDS command.

System programmer responseThe error status portion of this message contains the2-byte error code (S99ERROR) followed by the 2-byteinformation code (S99INFO) from the SVC requestblock. Refer to the appropriate MVS publication for adescription of these codes.

DSNJ303I WRITE ERROR ON REPLACEMENTBSDS DSNAME=... ERRORSTATUS=...

ExplanationThe -RECOVER BSDS command encountered an errorwhile attempting to write to the specified bootstrapdata set. Error Status contains the VSAM return andfeedback codes. It is a 2-byte field with the firstcontaining the hexadecimal return code and thesecond containing the hexadecimal feedback code.



System programmer responseExecute an offline access method services job todelete or rename the replacement BSDS and define anew BSDS with the same name. Reenter the logmanager -RECOVER BSDS command to reestablishdual BSDS mode.

DSNJ304I ERROR CLOSING REPLACEMENTBSDS DSNAME=... ERRORSTATUS=...

ExplanationThe -RECOVER BSDS command encountered an errorwhile attempting to close the specified bootstrap dataset. Error Status contains the VSAM return andfeedback codes. It is a 2-byte field with the firstcontaining the hexadecimal return code and thesecond containing the hexadecimal feedback code.



System programmer responseExecute an offline access method services job todelete or rename the replacement BSDS and define anew BSDS with the same name. Reenter the log


manager -RECOVER BSDS command to reestablishdual BSDS mode.

DSNJ305I REPLACEMENT BSDS NOT EMPTYDSNAME=...

ExplanationThe -RECOVER BSDS command was issued, but thereplacement bootstrap data set was not empty; that is,it contained data.

System actionProcessing of the command is terminated. Db2continues in single BSDS mode.


System programmer responseExecute an offline access method services job todelete or rename the error BSDS and define a newBSDS with the same name. Reenter the log manager -RECOVER BSDS command to reestablish dual BSDSmode.

DSNJ306I DUAL BSDS MODE ALREADYESTABLISHED

ExplanationThe -RECOVER BSDS command was issued, but Db2was already in dual BSDS mode.

System actionThe command is ignored.

DSNJ307I LOG INITIALIZED IN SINGLEBSDS MODE

ExplanationThe -RECOVER BSDS command was issued, but thesystem was initialized in single BSDS mode.


DSNJ310I (A)SYNCHRONOUS ARCHIVE LOGCOMMAND QUIESCE PROCESSINGSTARTED FOR MAXIMUM OF xxxSECONDS

ExplanationAn -ARCHIVE LOG command with the MODE(QUIESCE)option has been accepted by the Db2 subsystem. Thequiesce processing has commenced.

System actionThe Db2 subsystem will attempt to stop all updates toDb2 resources within the time period specified in themessage. Users/jobs operating on the Db2 subsystemwill be allowed to reach a point of consistency (commitpoint) before being blocked from further updateactivity. Jobs and users will be suspended until theyare released by Db2 following the initiation of theoffload processing. If the Db2 subsystem caneffectively block all users from performing updatesbefore the maximum specified time, the offload will beinitiated immediately, and normal processing will beresumed.

The message will display either the wordSYNCHRONOUS or ASYNCHRONOUS, to inform theuser of the type of quiesce processing which has beenused.

• If the word SYNCHRONOUS is displayed, then theinvoker used the WAIT(YES) option. This means thatquiesce processing will be synchronous to the user;that is, the user can enter additional Db2 commands,but the commands will not be processed by the Db2command processor until the quiesce processinghas ended.

• If the word ASYNCHRONOUS is displayed, then theinvoker used the WAIT(NO) option, or did not specifythe WAIT option. This means that quiesceprocessing will be asynchronous to the user; that is,control will be returned to the invoker as soon as thequiesce task has been started. Thus, the Db2command processor will accept - and process - anynew Db2 commands while the quiesce task isrunning.

This message will be followed by message DSNJ311Ior DSNJ317I.

Operator responseNo operator response is necessary. However, it can beexpected that users and jobs using Db2 resources willbe suspended (queued) by Db2 through the duration ofthe specified time interval, or until the Db2 subsystemcan be certain that all update activity has beeneffectively blocked. At some point, this message willbe followed by the DSNJ311I message or DSNJ317Imessage.


DSNJ311I csect-name ASYNCHRONOUS LOGARCHIVE (OFFLOAD) TASKINITIATED

ExplanationA user-initiated -ARCHIVE LOG command has beenaccepted by the Db2 subsystem. An asynchronoustask to archive (offload) the active log data set hasbeen started.

System actionThe current active log data set(s) will be truncated andswitched to the next available active log data set(s),and an asynchronous offload task will be initiated toarchive the Active log data set(s).

The term ASYNCHRONOUS is used to indicate thatcontrol will be returned to the invoker as soon as theoffload task has been started. Thus, the Db2 commandprocessor will accept and process any Db2 commandswhile the offload task is running.

This message is followed by message DSNJ312I if theMODE(QUIESCE) option was used with the -ARCHIVELOG command.

Operator responseThe operator should respond per normal operationalprocedures when the offload task begins.

DSNJ312I ARCHIVE LOG QUIESCE ENDED.UPDATE ACTIVITY AGAINST DB2RESOURCES IS NOW RESUMED.

ExplanationAn -ARCHIVE LOG command with the MODE(QUIESCE)option was processed by the Db2 subsystem. As partof the MODE(QUIESCE) processing, an attempt wasmade to stop all new update activity against Db2resources. This message signals the end of the quiesceprocessing, and the resumption of normal Db2 activityfor all users and jobs which were blocked during thequiesce period.

This message follows message DSNJ311I orDSNJ317I.

System actionThe Db2 subsystem has now resumed all normal Db2activity for all users and jobs that were blocked duringthe quiesce period.

DSNJ313I PARAMETER SPECIFIED ON THEkeyword KEYWORD (value) IS NOT

IN THE RANGE OF ALLOWABLEVALUES

ExplanationThis message was generated by an error occurring inone of the following commands:

• ARCHIVE LOG command with MODE(QUIESCE)• SET ARCHIVE• SET LOG

You specified a value for one of the command optionsthat was outside of the range of allowed values.

System actionProcessing for the ARCHIVE LOG, SET ARCHIVE, orSET LOG command is terminated. This message isfollowed by message DSN9023I.

Operator responseCorrect the syntax and reissue the command.

Related reference-ARCHIVE LOG (Db2) (Db2 Commands)-SET ARCHIVE (Db2) (Db2 Commands)-SET LOG (Db2) (Db2 Commands)Related informationDSN9023Icsect-name verb-name pkw-name ABNORMALCOMPLETION

DSNJ314I keyword-1 KEYWORD REQUIRESkeyword-2 KEYWORD TO ALSO BESPECIFIED ON THE COMMAND

ExplanationA command was entered which specified thekeyword-1 keyword. However, use of the keyword-1keyword requires that the keyword-2 keyword also beused.

System actionCommand processing terminates for the -ARCHIVELOG or -RECOVER BSDS command. This message isfollowed by message DSN9023I.


Related reference-ARCHIVE LOG (Db2) (Db2 Commands)-RECOVER BSDS (Db2) (Db2 Commands)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_archivelog.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_setarchive.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_recoverbsds.html

Related informationDSN9023Icsect-name verb-name pkw-name ABNORMALCOMPLETION

DSNJ315I -STOP DB2 MODE(FORCE) INPROGRESS

ExplanationAn attempt was made to issue an -ARCHIVE LOGcommand when a -STOP DB2 MODE(FORCE)command was already in progress.

System actionCommand processing terminates for the -ARCHIVELOG command. The -STOP DB2 MODE(FORCE)processing continues.

DSNJ316I SYSTEM QUIESCE ALREADY INPROGRESS

ExplanationAn attempt was made to issue an -ARCHIVE LOGcommand with the MODE(QUIESCE) option when asystem quiesce was already in progress. The systemquiesce could be the result of processing by another -ARCHIVE LOG MODE(QUIESCE) command, or by a -STOP DB2 MODE(QUIESCE) command.

System actionCommand processing will terminate. The systemquiesce currently in progress will continue.

DSNJ317I ARCHIVE LOG QUIESCE PERIODEXPIRED. NUMBER OFOUTSTANDING UR'S = xxxx.ARCHIVE LOG PROCESSING WILLBE TERMINATED, AND UPDATEACTIVITY AGAINST DB2RESOURCES WILL BE RESUMED.HH:MM:SS

ExplanationAn -ARCHIVE LOG MODE(QUIESCE) command wasprocessed by the Db2 subsystem; however, the Db2subsystem was not able to quiesce all update activityin the user-specified quiesce time interval.

System actionThis message is informational only. The Db2subsystem determined that 'xxxx' units of recovery(URs) did not reach a point of consistency during the

quiesce period, and therefore could not be stoppedfrom continuing their associated update processing.

Consequently, the -ARCHIVE LOG processing will beterminated. The current active log data set(s) will notbe truncated, and will not be switched to the nextavailable active log data set(s). The log archive(offload) task will not be created. All jobs and userssuspended during the quiesce will be resumed, andnormal update activity against Db2 resources will becommenced.

This message will be followed by the DSNJ312Imessage.

Operator responseContact the system programmer.

System programmer responseA determination must be made whether theoutstanding (non-quiesced) URs represent significantwork.

Each user on the system has a unit of recovery if theyare modifying Db2 resources. URs are also created bythe Db2 subsystem itself for internal processing. Sincethe purpose of the MODE(QUIESCE) option is to haveall URs reach a point of consistency (commit point)before the active log data set is truncated andoffloaded, determine all outstanding non-queued jobsand users by using -DISPLAY THREAD and the MVS 'DA,L' operator command.

It should be noted that URs may be outstanding due tolock contention between a user or job which holds aresource (and has reached a point of consistency), anda user or job which wants a lock (and therefore cannotreach a point of consistency).

Before resubmitting the -ARCHIVE LOG command withthe MODE(QUIESCE) option, either:

• Wait until the threads have been deallocated.• Wait until the Db2 subsystem is less busy.• Force the offending thread(s) to terminate.• Use the TIME option to dynamically override and

extend the maximum quiesce time period specifiedin subsystem parameters.

• Or, if having all URs reach a point of consistency inthe active log is no longer critical, issue the -ARCHIVE LOG command without theMODE(QUIESCE) option.

Important: If the decision is made to use the -ARCHIVE LOG command without the MODE(QUIESCE)option, the active log data set(s) will be truncatedwithout regard to quiescing activity on the Db2subsystem. If the resulting archive log data set is used


for recovery, it is possible that some URs may be foundto be inflight, in-abort, in-commit, or indoubt duringDb2 initialization.

If expiration of the quiesce period before all URs reacha consistent point are a chronic problem, you mightneed to adjust the value of the QUIESCE subsystemparameter.

Related referenceQUIESCE PERIOD field (QUIESCE subsystemparameter) (Db2 Installation and Migration)-ARCHIVE LOG (Db2) (Db2 Commands)Related informationDSNJ312IARCHIVE LOG QUIESCE ENDED. UPDATEACTIVITY AGAINST DB2 RESOURCES IS NOWRESUMED.

DSNJ318I ARCHIVE LOG COMMANDALREADY IN PROGRESS

ExplanationAn attempt was made to issue an ARCHIVE LOGcommand when an ARCHIVE LOG command wasalready in progress. In data sharing, the ARCHIVE LOGcommand currently in progress could be initiated byanother member.

Operator responseIf the conflicting command satisfies your archivalrequest, do not reissue the command. Otherwise, waitfor the conflicting command to complete and thenreissue the -ARCHIVE LOG command.

DSNJ319I csect name CURRENT ACTIVE LOGDATA SET IS THE LAST AVAILABLEACTIVE LOG DATA SET. ARCHIVELOG PROCESSING WILL BETERMINATED.

ExplanationThe -ARCHIVE LOG command was rejected becausethe current active log is the last available active logdata set. To process the command when theseconditions exist would cause the Db2 subsystem toexhaust its available active log resources andimmediately halt processing.

System actionProcessing for the command is terminated. If thesituation is not corrected, the Db2 subsystem willissue the DSNJ110E message (if it has not alreadydone so) as the available active log data space reachescritically low levels. Ultimately, message DSNJ111E

will be issued when the available active log data spaceis exhausted, and the Db2 online processing will haltuntil active log space is made available.

Operator responseTo clear this condition, steps must be taken tocomplete other waiting offload tasks. Once anotheractive log is made available (re-usable) by completingthe offload process for it, the command processing forthe current active log can proceed.

Execute an MVS Display System Requests command (DR,L for example) to determine the outstandingrequests related to the log offload process. Take thenecessary action to satisfy any requests, and permitoffload to continue. If offload fails to completenormally, or cannot be initiated, notify the systemsprogrammer.

System programmer responseEither correct the problem that is causing the offloadprocess to fail, or add more active log data sets. Notethat the latter action requires Db2 to be down and thechange log inventory (DSNJU003) utility to be run.

Possible causes for the shortage of active log dataspace are:

• Excessive logging. For example, too many usersrequesting logs at the same time, or too manyutilities specifying LOG (YES).

• Delayed or slow offloading. For example, failure tomount archive volumes, incorrect replies to offloadmessages, or slow device speeds.

• Excessive use of the -ARCHIVE LOG command. Eachinvocation of the command causes the Db2subsystem to switch to a new active log data set.Excessive use could consume the available active logdata space if the resulting offloads were notprocessed in a timely manner.

• Off-loads(s) failed (see Operator Response).• Insufficient active log space (see Operator

Response).

User responseNotify the operator or system programmer.

DSNJ320I csect-name UNABLE TO PROCESSLOG TRUNCATION REQUEST DUETO SUBSYSTEM COMPONENTaction FAILURE


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_quiesce.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_quiesce.html


ExplanationWhile processing an -ARCHIVE LOG command, aninternal request was made of the log buffer outputroutine to force-write the log buffers and to truncateand switch the active log to the next available activelog data set(s). The request failed during theprocessing of the 'action' specified in the message.

System actionProcessing for the command is terminated.


System programmer responseThis error is an internal error detected by the Db2subsystem. The error may be caused by an unrelatedABEND in the Log Buffer Writer component(DSNJWxxx), by a -STOP DB2 MODE(FORCE)command, or by abnormal subsystem termination.Refer to messages and ABENDS which precede thismessage.


DSNJ321I UNABLE TO CONTINUE ARCHIVELOG QUIESCE DUE TO INTERNALSUBSYSTEM ERROR. ARCHIVELOG PROCESSING WILL BETERMINATED, AND UPDATEACTIVITY AGAINST DB2RESOURCES WILL BE RESUMED.

ExplanationAn -ARCHIVE LOG command with the MODE(QUIESCE)option was processed by the Db2 subsystem. As partof the MODE(QUIESCE) processing, an attempt wasmade to stop all new update activity against Db2resources. During the internal subsystem interactionbetween the log manager and the recovery manager,an internal interface error was detected by therecovery manager.

System actionThe -ARCHIVE LOG MODE(QUIESCE) processing isterminated. This message will be followed by messageDSNJ312I after all users and jobs quiesced by theMODE(QUIESCE) processing are resumed.


System programmer responseThis error is an internal error detected by the Db2subsystem. Retry the -ARCHIVE LOG MODE(QUIESCE)command. If the error persists, the active log data setsmay be switched using the -ARCHIVE LOG commandwithout the MODE(QUIESCE) option.


DSNJ322I DISPLAY ARCHIVE REPORTFOLLOWS—

ExplanationThis message displays output from the DISPLAYARCHIVE command. This output contains informationabout archive log data sets that are in use for thesubsystem or data-sharing member. For data-sharingenvironments, it does not include information aboutthe entire group.

The output begins with the following lines thatdescribe the basic characteristics of the archive unitsfor reading the archive logs:

DSNJ322I -DISPLAY ARCHIVE REPORT FOLLOWS- COUNT TIME (TAPE UNITS) (MIN,SEC)name count timename count time

nameAn identifier for the count and time values thatfollow on the same line.

name can have one of the following values:

DSNZPARMThe count and time values that follow are thevalues that were specified during Db2installation. These values correspond to thefollowing subsystem parameters:

• The count value is from the MAXRTUsubsystem parameter.

• The time value is from the DEALLCTsubsystem parameter.

CURRENTThe count and time values that follow are thecurrent values in the Db2 subsystem. Thesevalues might be the same as the subsystemparameter values that are listed in theDSNZPARM line. However, if those values were


overridden by the SET ARCHIVE command, thisline lists those changed values.

countThe maximum number of tape units that can beallocated to concurrently read archive log tapevolumes.

timeThe length of time that an allocated archive readtape unit can remain unused before it isdeallocated. The format is minutes,seconds.

After the information about archive units, the outputcontains the following lines:

===============================================ADDR STAT CORR-ID VOLSER DATASET_NAME addr status corr-id vname dsname...END OF DISPLAY ARCHIVE REPORT.

These lines describe the archive log data sets that arebeing read. After the heading information, one line isdisplayed for each archive log data set that is beingread. Each of those lines includes the followinginformation:

addrThe physical address of the device that is allocatedto read the archive log.

statusThe status of the device, which can be one of thefollowing values:BUSY

The device is actively processing an archive logdata set.

PREMThe device is active and allocated forpremount.

AVLThe device is inactive and waiting for work.

RCALThe archive data set is being recalled by HSM.

corr-idThe correlation id that is associated with the userof the device that is being processed. If the statusis PREM or AVL, this column might contain *****,which indicates that a current user is notassociated with this device.

vnameThe name of the archive volume that is mounted atthe device address.

dsnameIf status is BUSY, PREM or RCAL, the name of thedata set on the archive volume that is beingprocessed.

If status is AVL, the name of the data set on thearchive volume that was last processed.

If no archive logs are currently being read, thefollowing message is displayed instead of the linesthat describe the archive log data sets:

NO ARCHIVE READ ACTIVITY



Related reference-DISPLAY ARCHIVE (Db2) (Db2 Commands)-SET ARCHIVE (Db2) (Db2 Commands)READ TAPE UNITS field (MAXRTU subsystemparameter) (Db2 Installation and Migration)DEALLOC PERIOD field (DEALLCT subsystemparameter) (Db2 Installation and Migration)

DSNJ330I ARCHIVE LOG VOLUMESREQUIRED FOR CONNECTION IDconn-id CORRELATION ID corr-id

ExplanationThis message is the title for the ARCHIVE LOGVOLUMES report output. The ARCHIVE LOG VOLUMESreport lists the archive log volumes needed by thecorrelation ID for that connection ID. This message isgenerated automatically by the archive read process atthe first archive log tape mount for corr-id. Thismessage precedes the other messages generated bythis action.

This message, in combination with messagesDSNJ331I and DSNJ332I, provides the formattedreport for the ARCHIVE LOG VOLUMES requested.conn-id

An identifier representing the 'connection name'used to establish the thread.

corr-idAn identifier associated with a specified thread. InTSO, it is either the authorization ID or the jobname.

DSNJ331I avolume, avolume, avolume,avolume ...

ExplanationThis message provides the tape volume informationfor the Archive Log Volumes report output.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displayarchive.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_maxrtu.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_maxrtu.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_deallct.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_deallct.html

avolumeThe name of the archive log volume required forthis correlation ID. An 'avolume' prefixed with an '*'signifies that the data on the archive log volume isalso mapped by an active log data set. As such, the'avolume' might not be required for the readprocess, since the data is read from the active log,if possible.

DSNJ332I END OF ARCHIVE LOG VOLUMESREPORT

ExplanationThis message follows messages DSNJ330I andDSNJ331I and indicates that the ARCHIVE LOGVOLUMES report was generated successfully. Themessage number is not included in this message.

DSNJ333I csect-name SYSTEM CHECKPOINTINITIATED

ExplanationThis message indicates that the SET LOG commandprocessed successfully and that a system checkpointhas been initiated.

DSNJ334I PARAMETER SPECIFIED ON THEkeyword KEYWORD (VALUE)CONTAINS INVALID CHARACTERS

ExplanationA -SET ARCHIVE command was processed by the Db2subsystem. One of the command keywords specified avalue that contains an invalid character.

System actionProcessing for the -SET ARCHIVE command isterminated. This message is followed by theDSN9023I message.


Related reference-SET ARCHIVE (Db2) (Db2 Commands)Related informationDSN9023Icsect-name verb-name pkw-name ABNORMALCOMPLETION

DSNJ335I INVALID KEYWORDSCOMBINATION IN SET ARCHIVECOMMAND

ExplanationThis command requires that keyword COUNT orkeyword TIME be specified. If both are omitted, thekeyword DEFAULT must be specified. It is invalid tospecify keyword DEFAULT when either the COUNTkeyword or TIME keyword is specified.

System actionProcessing for the -SET ARCHIVE command isterminated. This message is followed by theDSN9023I message.


Related reference-SET ARCHIVE (Db2) (Db2 Commands)Related informationDSN9023Icsect-name verb-name pkw-name ABNORMALCOMPLETION

DSNJ336I UNABLE TO ALLOCATE TAPE UNITFOR conn-id corr-id, x ALLOCATED,y ALLOWED.

ExplanationAn attempt to allocate a tape unit for connection ID'conn-id' failed. The current maximum tape unitspecified is 'y', but only 'x' are physically available.

System actionThe 'conn-id corr-id' process is queued until either anallocated tape unit becomes free or more tape unitsare varied online and made available to the Db2archive read task.

Operator responseThis situation rectifies itself over time as currentlyallocated tape units become available. To improvethroughput, vary additional tape units online and makethem available to Db2. Note that a queue rescan is notattempted until the -SET ARC READ COUNT commandis issued or when an allocated tape dismounts.

DSNJ337I SET ARCHIVE COMMANDCOMPLETED, COUNT (count) TIME(minute,second).




ExplanationThis message indicates that the -SET ARCHIVEcommand processed successfully and displays thecurrent values for COUNT and TIME.count

The value for the COUNT parameterminute

The 'minute' value for the TIME parametersecond

The 'second' value for the TIME parameter

DSNJ339I csect-name SET LOG COMMANDCOMPLETED, frequency-type(frequency-unit)

ExplanationThis message indicates that the SET LOG commandprocessed successfully, and displays the currentcheckpoint frequency. The checkpoint frequencyremains in effect until Db2 is restarted or until thevalue is modified by a SET LOG or SET SYSPARMcommand.


frequency-typeIdentifies how the checkpoint frequency isdetermined. Expected values are CHKTIME (for afrequency based on elapsed time) and LOGLOAD(for a frequency based on the number of logrecords that are written).

frequency-unitSpecifies the unit for the associated frequency-typevalue.

The checkpoint frequency is controlled by thefollowing fields on installation panel DSNTIPL1:

• CHECKPOINT TYPE (CHKTYPE subsystemparameter)

• RECORDS/CHECKPOINT (CHKFREQ and CHKLOGRsubsystem parameters)

• MINUTES/CHECKPOINT (CHKFREQ and CHKMINSsubsystem parameters)

Multiple forms: This message has two forms. Theshort form is shown above. The long form is:csect-name SET LOG COMMAND COMPLETED,frequency-type(frequency-unit) ORfrequency-type(frequency-unit)

The long form is used when both the number ofminutes and number of log records were changed bythe SET LOG command. The message shows thefrequency-type and frequency-unit values for both.

System actionProcessing continues, and Db2 issues a DSNJ371Imessage to show the current settings.

Related conceptsCheckpoint log records (Db2 AdministrationGuide)Related tasksChoosing a checkpoint frequency (Db2Performance)Related reference-SET LOG (Db2) (Db2 Commands)-SET SYSPARM (Db2) (Db2 Commands)DSNTIPL1: Checkpoint parameters (Db2Installation and Migration)Related informationDSNJ371IDB2 RESTARTED time-date-1 RESTART RBArstrt-rba CHECKPOINT FREQUENCY quantity-and-type LAST SYSTEM CHECKPOINT TAKENtime-date-2

DSNJ340I csect-name COMMAND KEYWORDxxx IS ONLY VALID FOR DATASHARING

ExplanationAn attempt was made to issue a Db2 command withKEYWORD xxx on a Db2 that was not initialized toparticipate in data sharing.

System actionThe command request is rejected.

DSNJ341I csect-name -ARCHIVE LOGCOMMAND NOT ALLOWED,LOGGING IS SUSPENDED

ExplanationAn attempt to issue an -ARCHIVE LOG command failedbecause a -SET LOG SUSPEND command hassuspended logging.

System actionCommand processing terminates for the -ARCHIVELOG command. You may reissue the command whenlogging has been resumed by the -SET LOG RESUMEcommand.

DSNJ350I csect-name (A)SYNCHRONOUSARCHIVE LOG COMMANDQUIESCE PROCESSING STARTEDIN DATA SHARING


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_checkpointlogrecord.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_choosecheckpointfreq.html




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntipl1.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntipl1.html

ExplanationThe Db2 subsystem of a data sharing group acceptedan ARCHIVE LOG command with the MODE(QUIESCE)option.

Each active Db2 member in the data sharing groupperforms the quiesce operation. The memberoriginating the quiesce issues message DSNJ350I; allother members issue DSNJ310I as they startquiescing.

DSNJ351I csect-name MEMBER membername STATUS=member status

ExplanationThis message is one of a list of elements that displayarchive related status of the indicated member of thedata sharing group. These member status messagesare preceded by the message DSNJ359I and arefollowed by DSNJ361I.

member name identifies the member of the datasharing group.

member status indicates archive related status of thenamed member. It appears as one of the following:.ABNORMALLY TERMINATING

The named member was undergoing abnormalsubsystem termination at the time ARCHIVE LOGprocessing was active for the data sharing group.ARCHIVE LOG command processing for theremainder of the data sharing group terminatesunsuccessfully.

ARCHIVE ALREADY ACTIVEARCHIVE LOG command processing was runningat the named member at the time a succeedingARCHIVE LOG command was issued. Thesucceeding ARCHIVE LOG command terminatesunsuccessfully for the remaining members of thedata sharing group.

CANCELEDARCHIVE LOG command processing for the namedmember was canceled due to a problemencountered elsewhere in the data sharing group.The quiesce operation is interrupted andterminated and update activity against Db2resources is resumed before command processingis terminated for the member.

COMMUNICATIONS FAILUREA communications failure occurred between thenamed member and one or more other membersin the data sharing group. The quiesce operation isinterrupted and update activity against Db2resources is resumed before command processingis terminated for the member. ARCHIVE LOG

command processing for the remainder of the datasharing group terminates unsuccessfully.

FAILEDThe named member was inactive at the time theARCHIVE LOG command was issued. Terminationof the Db2 subsystem for this member wasabnormal. This status, if displayed for any member,will cause ARCHIVE LOG command processing forthe entire data sharing group to terminateunsuccessfully.

NOT AVAILABLEArchive command status for the named membercould not be determined. This condition typicallyoccurs when the named member fails to respondduring ARCHIVE LOG command processing and isusually accompanied by message DSNJ353Iand/or message DSNJ355I.

QUIESCEDThe named member was active at the time theARCHIVE LOG command was issued. Updateactivity against Db2 resources had successfullyquiesced for that member (no active URs) inresponse to specifying MODE(QUIESCE).

QUIESCED/OFFLOADINGThe named member was active at the time theARCHIVE LOG command was issued. Updateactivity against Db2 resources had successfullyquiesced for that member (no active URs) inresponse to specifying MODE(QUIESCE). Theactive log at the time was truncated and an offloadprocess was initiated after all members in the datasharing group had reached a quiesce point.

STOPPEDThe named member was inactive at the time theARCHIVE LOG command was issued. Terminationof the Db2 subsystem for this member was normalwith no incomplete URs outstanding. Logtruncation and offload processing are scheduled tobe performed automatically the next time thenamed member is started. When the member isstarted, it is important to ensure that archiveprocessing occurs automatically. Certain errorconditions might require entering an ARCHIVE LOGcommand via the operator console to cause logtruncation and offload processing to be performed.This member status is accompanied by warningmessage DSNJ362A.

TIME EXCEEDEDThe named member could not quiesce its updateactivity within the allotted period of time. Theincomplete quiesce operation is interrupted andupdate activity is resumed before commandprocessing is terminated for the member. ARCHIVELOG command processing for the remainder of thedata sharing group is unsuccessfully terminated.


DSNJ352W csect-name MEMBERS WERE NOTOFFLOADED

ExplanationDb2 issues this message during processing of anARCHIVE LOG command with the MODE(QUIESCE)option. One or more quiesced members were notavailable to receive the archive request. DSNJ351Imessages follow to display the quiesced members.

At the next start up of the quiesced member, Db2switches (truncates) the current active log and initiatesthe archive task.

DSNJ353I csect-name DSNJ353I MEMBERmember name NOT RESPONDING.

ExplanationThis message is displayed when a response is neededbut not received within an expected period of timeduring ARCHIVE LOG MODE(QUIESCE) commandprocessing. This can occur as a result of abnormalsubsystem termination under the named member or,possibly from communications problems amongmembers of the data sharing group.

Operator responseExamine the console log of the named member foroperator information messages that might relate to theproblem.

DSNJ354I csect-name DSNJ354I ARCHIVELOG: ALL ACTIVE MEMBER(S)STARTED OFFLOAD TASKS

ExplanationThis message is displayed when MODE(QUIESCE) isspecified with the ARCHIVE LOG command, after allactive members in the data sharing group havesuccessfully quiesced their update activity within theallotted time period. For each active member in thedata sharing group, the active log is truncated andswitched, and an offload task is initiated to begin theoffload process. Log truncation, switch and offloadprocessing for stopped (and quiesced) members isperformed the next time they are started.

DSNJ355I csect-name ARCHIVE LOG: ONE ORMORE ACTIVE MEMBERS FAILEDTO RESPOND OR START OFFLOADTASKS

ExplanationThis message is displayed when MODE(QUIESCE) isspecified with the ARCHIVE LOG command, and one ormore active members could not successfully quiescetheir update activity in the time allotted. Subsystemactivity already quiesced is resumed, and ARCHIVELOG command processing terminates unsuccessfullyfor all active members in the data sharing group.Message DSNJ353I might also appear with thismessage.

Operator responseSee the list of DSNJ351I member status messagesfollowing message DSNJ359I to determine the reasonfor the archive command failure.

DSNJ356I csect-name COMMUNICATIONSFAILURE TERMINATED COMMAND

ExplanationThis message appears as a result of the failure of acommunications request by one or more members ofthe data sharing group. This message is likely to beaccompanied by DSN7xxx or other error messagesand/or an SVC dump.

System actionARCHIVE LOG command processing terminatesunsuccessfully for all members in the group.

DSNJ357E csect-name SYSTEM QUIESCEFAILED

ExplanationThis message indicates the unsuccessful outcome ofan ARCHIVE LOG MODE(QUIESCE) command. Thismessage indicates that one or more members wereunable to quiesce their update activity in the timeallowed. It is usually accompanied by one or morerelated messages (e.g., DSNJ355I), and a list ofmember status messages indicating the reason for thefailure.

Operator responseRefer to messages DSNJ359I, DSNJ351I andDSNJ361I to determine archive related status ofmembers in the data sharing group.

DSNJ359I MEMBER RESPONSES


ExplanationThis message marks the beginning of a list of one ormore DSNJ351I member status messages andprecedes the first status message in the list.

DSNJ361I csect-name END OF MEMBERRESPONSES LIST

ExplanationThis message marks the end of a list of one or moreDSNJ351I member status messages and follows thelast status message in the list.

DSNJ362E csect-name WARNING: LOGS OFnn STOPPED OR FAILED MEMBERSNOT OFFLOADED.

ExplanationThis message is displayed when eitherMODE(QUIESCE) or SCOPE(GROUP) is specified withthe ARCHIVE LOG command, and one or moremembers of the data sharing group either stopped orfailed and were not available to receive the archiverequest. Active log truncation, log switch and offloadprocessing for these inactive members is scheduled tobe performed the next time those members arestarted.

Operator responseVerify that log switch and offload processing doesautomatically occur when the inactive members arestarted. Certain error conditions might require theARCHIVE LOG command to be individually issued for amember if ARCHIVE LOG processing does not occurautomatically. Refer to messages DSNJ359I,DSNJ351I, and DSNJ361I to identify the inactivemembers.

DSNJ363I csect-name COPY log-copy LOGDATA SET dataset-name ADDED TOTHE ACTIVE LOG INVENTORY

ExplanationThe active log data set identified bydataset-name wassuccessfully added to active log inventory with the SETLOG command. The log data set is now available foruse by Db2.


log-copyThe new log copy.




Related reference-SET LOG (Db2) (Db2 Commands)

DSNJ364I NEWLOG OPERATION FAILED.REASON: reason-string

ExplanationThe NEWLOG option of the SET LOG command hasfailed. The value of reason-string describes the causeof the failure:OPEN ERROR

An error occurred attempting to allocate or openthe new log data set. Make sure that the NEWLOGdata set name is correct and that the data set hasbeen defined correctly with IDCAMS.

BSDS ERRORAn error occurred attempting to update the BSDS.

DUPLICATE LOG DATA SET NAMEThe specified log data set name already exists inthe current active log inventory. Make sure that theNEWLOG data set name is correct.

LOG COPY AT MAXIMUM NUMBER OF LOGSThe specified log copy already contains themaximum number of active log data sets. You canspecify up to a maximum of 93 log data sets peractive log copy.

COPY2 IN SINGLE LOGGING MODECOPY(2) was specified but Db2 was started insingle logging mode.

OUT OF SPACE IN BSDSThere is no space in the BSDS to add the new logdata set information. This failure indicates apossible problem with the BSDS control record. Ifthe problem persists, contact IBM Support Preparean IDCAMS PRINT of the BSDS.

COMMAND ABENDEDAn ABEND occurred during command processing.

System actionThe command terminates.



User responseExamine the console log for messages related to thefailure.

Related reference-SET LOG (Db2) (Db2 Commands)

DSNJ370I csect-name LOG DISPLAYCURRENT COPY1 LOG = dsname1IS pct1% FULL CURRENT COPY2LOG = dsname2 IS pct2% FULLH/W RBA = hw-rba, H/O RBA = ho-rba FULL LOGS TO OFFLOAD = full-count OF total-count, OFFLOADTASK IS status SOFTWAREACCELERATION IS accel-status

ExplanationThis message displays output from the DISPLAY LOGcommand. The output from this command has thefollowing general structure:

DSNJ370I csect-name LOG DISPLAYCURRENT COPY1 LOG = dsname1 IS pct1% FULL

CURRENT COPY2 LOG = dsname2 IS pct2% FULL

H/W RBA = hw-rba H/O RBA = ho-rba FULL LOGS TO OFFLOAD = full-count OF total-count OFFLOAD TASK IS status SOFTWARE ACCELERATION IS ENABLED

DSNJ371I DB2 RESTARTED time-date-1 RESTART RBA rstrt-rba CHECKPOINT FREQUENCY quantity-and-type LAST SYSTEM CHECKPOINT TAKEN time-date-2DSN9022I -DB2A DSNJC001 '-DIS LOG' NORMAL COMPLETION

When both the number of minutes and the number oflog records are used to determine the checkpointfrequency, the output includes the followingalternative form of message DSNJ371I, which showsboth values:

DSNJ371I DB2 RESTARTED time-date-1 RESTART RBA rstrt-rba CHECKPOINT FREQUENCY quantity-and-type OR quantity-and-type LAST SYSTEM CHECKPOINT TAKEN time-date-2

When the log is on a member of a data sharing groupthat is a component of a GDPS® Continuous Availabilitywith zero data loss solution, message DSNJ375Ifollows message DSNJ371I:

DSNJ375I csect-name CDDS DSNAME=dsname3 IS cdds-status IN cdds-mode MODE.


dsname1The name of the current active log COPY 1 dataset. This data set is used for the first copy of theactive log. If the value for dsname1 is INACTIVE,this copy of the log is not currently active.

pct1The percentage of log space in the active log COPY1 data set that has been used for writing logrecords.

dsname2The name of the current active log COPY 2 dataset. This data set is used for the second copy of theactive log. If the value for dsname2 is INACTIVE,this copy of the log is not currently active.

pct2The percentage of log space in the active log COPY2 data set that has been used for writing logrecords.

hw-rbaThe RBA of the most recently written log record.

ho-rbaThe highest log RBA that has been offloaded to anarchive log data set.

full-countThe number of full active log data sets that havenot been archived.

total-countThe total number of active log data sets.

statusThe status of the offload task. status can be one ofthe following values:BUSY,ALLC

The task is busy allocating an archive log dataset. This status might indicate that a tapemount request is outstanding.

BUSY,BSDSThe task is busy copying the bootstrap data set(BSDS).

BUSY,ACTVThe task is busy copying an active log data set.

BUSYThe task is busy with other processing.

AVAILABLEThe task is available for work.

accel-statusThe status of software-controlled mirroring, eitherENABLED or DISABLED based on the setting of theREMOTE_COPY_SW_ACCEL subsystem parameter.



time-date-1The time and date when Db2 started.

rstrt-rbaThe RBA that Db2 began logging when it started.

quantity-and-typeThe number of minutes or the number of logrecords that determine the current checkpointfrequency.

time-date-2The time and date of the last system checkpoint.

dsname3The name of the compression dictionary data set(CDDS) that interprets the log.

cdds-statusThe status of the CDDS. cdds-status can be one ofthe following values:ACTIVE

The CDDS is accessible for read/write access inthe source data sharing group. The CDDS isaccessible for read/only access in the proxydata sharing group.

INACTIVEThe CDDS is not accessible for read/writeaccess in the source data sharing group. TheCDDS is not accessible for read/only access inthe proxy data sharing group.

cdds-modeThe purpose of the data sharing group to which thelog belongs:SOURCE

The data sharing group supports replication ofits log data sets by another data sharing group.

PROXYThe data sharing group supports replication oflog data sets for another data sharing group.

Related conceptsCheckpoint log records (Db2 AdministrationGuide)Related tasksChoosing a checkpoint frequency (Db2Performance)Related referenceLOG COPY 1, BSDS 2 field (Db2 Installation andMigration)LOG COPY 2, BSDS 1 field (Db2 Installation andMigration)CHECKPOINT TYPE field (CHKTYPE subsystemparameter) (Db2 Installation and Migration)RECORDS/CHECKPOINT field (CHKFREQ andCHKLOGR subsystem parameters) (Db2Installation and Migration)-DISPLAY LOG (Db2) (Db2 Commands)

Related informationDSN9022Icsect-name 'verb-namepkw-name' NORMALCOMPLETION

DSNJ371I DB2 RESTARTED time-date-1RESTART RBA rstrt-rbaCHECKPOINT FREQUENCYquantity-and-type LAST SYSTEMCHECKPOINT TAKEN time-date-2

ExplanationThis message is part of the output from the DISPLAYLOG command, which is described in message“DSNJ370I” on page 304.

DSNJ372I csect-name UPDATE ACTIVITYHAS BEEN SUSPENDED FOR aaaaAT RBA xxxxxxxxxxxx, LRSNyyyyyyyyyyyy, PRIORCHECKPOINT RBA zzzzzzzzzzzz

ExplanationThis message indicates that the -SET LOG commandwith the SUSPEND option has completed successfully.

System actionAll log and database update activity has beensuspended for Db2 subsystem aaaa. xxxxxxxxxxxxcontains the RBA of the last record written to the log.In a data sharing environment, yyyyyyyyyyyy containsthe LRSN of the last record written to the log.Otherwise, yyyyyyyyyyyy contains the high writtenRBA. zzzzzzzzzzzz contains the RBA of the last systemcheckpoint.


Operator responseIssue the -SET LOG command with the RESUMEkeyword when ready to resume update activity.

DSNJ373I csect-name UPDATE ACTIVITYHAS BEEN RESUMED FOR xxxx

ExplanationThis message indicates that the -SET LOG commandwith the RESUME option has completed successfully.

System actionAll log and database update activity has been resumedfor Db2 subsystem xxxx.






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_logcopy1bsds2.html




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_chktype.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_chktype.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_chkfreqandchklogr.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displaylog.html

DSNJ374I csect-name SET LOG optionsCOMMAND FAILED, reason

ExplanationA -SET LOG command has failed. options werespecified on the command. reason describes the causeof the failure:ALREADY SUSPENDED

A -SET LOG SUSPEND command was issued whileupdate activity was suspended by a previouscommand.

Db2 STOPPINGA -SET LOG SUSPEND command was issued, butDb2 is stopping.

QUIESCE ACTIVEA -SET LOG SUSPEND command was issued, but asystem quiesce that was initiated by an -ARCHIVELOG command is in progress.

NOT SUSPENDEDA -SET LOG RESUME command was issued, butupdate activity is not suspended.

COMMAND ABENDA -SET LOG command abnormally terminated.Update activity is not suspended.

LOCK TIMEOUTA lock timeout has occurred. Update activity is notsuspended.

System actionCommand processing terminates.

DSNJ375I csect-name CDDSDSNAME=dsname3 IS cdds-statusIN cdds-mode MODE.

ExplanationThis message is part of the output from the DISPLAYLOG command, which is described in message“DSNJ370I” on page 304. This message is also issuedduring Db2 startup in a GDPS Continuous Availabilitywith zero data loss (GDPS Continuous Availability withzero data loss) environment.


dsname3The name of the compression dictionary data set(CDDS) that interprets the log.

cdds-statusThe status of the CDDS. cdds-status can be one ofthe following values:

ACTIVEThe CDDS is accessible for read/write access inthe source data sharing group. The CDDS isaccessible for read/only access in the proxydata sharing group.

INACTIVEThe CDDS is not accessible for read/writeaccess in the source data sharing group. TheCDDS is not accessible for read/only access inthe proxy data sharing group.

cdds-modeThe purpose of the data sharing group to which thelog belongs:SOURCE

The data sharing group supports replication ofits log data sets by another data sharing group.

PROXYThe data sharing group supports replication oflog data sets for another data sharing group.

DSNJ376I csect-name CDDS INITIALIZATIONFAILED. CDDS SERVICES AREUNAVAILABLE.

ExplanationAn error occurred during initialization of thecompression dictionary data set (CDDS).

System actionCDDS initialization was terminated.


System programmer responseThis error is an internal error detected by the Db2subsystem.


DSNJ377I csect-name CDDS ALLOCATIONERROR FOR DSNAME=dataset-name, ERROR STATUS=status-indicator, SMS REASONCODE=ssssssss.

ExplanationThe log manager encountered an error while itattempted to allocate the specified compressiondictionary data set (CDDS).




status-indicatorThe error reason code that is returned by z/OS MVSdynamic allocation (SVC99). This value consists ofa 2-byte error code (S99ERROR) followed by a 2-byte information code (S99INFO) from the SVC99request block.

ssssssssIf available, more SMS reason code informationfrom S99ERSN, which is a field of S99RBX.ssssssss is displayed if the S99ERROR codeindicates an SMS allocation error (97xx).

System action


System programmer response

DSNJ378I csect-name CDDS DEFINEATTRIBUTE ERROR FORDSNAME=dataset-name.

ExplanationOne or more attributes of the compression dictionarydata set (CDDS) was incorrectly specified.



System actionCDDS processing was terminated.


System programmer responseCheck whether the data set allocation attributes forthe CDDS are specified correctly.


Problem determinationRun LISTCAT on the CDDS, and compare the data setattributes to those that are specified in Modifying Db2for the GDPS Continuous Availability with zero dataloss solution (Db2 Administration Guide).

DSNJ379I csect-name function ERROR ONCDDS DSNAME=dataset-name.

ExplanationAn error occurred when the specified function wasperformed on the specified compression dictionarydata set (CDDS).


functionThe function that was performed on the CDDS.






DSNJ380I csect-name OUT OF SPACE INCDDS DSNAME=dataset-name.

ExplanationThe specified compression dictionary data set (CDDS)does not have any more space. The operation thatencountered the out-of-space condition did notcomplete properly.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_upgradedb2forgdpsaa2.html




System actionAn error code is returned to the log request thatcaused access to the CDDS.


System programmer responseFollow these steps to avoid data loss while defining anew, larger CDDS:

1. Stop replication by the proxy group to avoid dataloss. If you are using a replication product that usessubscription sets, stopping replication avoids theneed to refresh a large number of subscription sets.

2. Stop one of the least active members of the sourcedata sharing group.

3. Delete the CDDS, and define a larger CDDS with thesame name.

4. Start the member of the source data sharing groupthat you stopped. This action causes system controlrecords to be inserted in the new CDDS.

5. Run REORG TABLESPACE with the INITCDDS optionon one of the following sets of table spaces:

• All table spaces that contain tables that aredefined with DATA CAPTURE CHANGES

• All table spaces that contain tables that are inreplication subscription sets

6. Start replication by the proxy group.


DSNJ381I csect-name CDDS CONTROLRECORD ERROR FORDSNAME=dataset-name, REASONCODE=reason-code.

ExplanationA request to read from or write to the system controlrecord in the specified compression dictionary data set(CDDS) failed.






System programmer responseThis error is an internal error detected by the Db2subsystem. See the description of the reason code thatis specified in the message text for more informationabout the error.


Related information00D10A0C (Db2 Codes)00D10A0D (Db2 Codes)00D10A0E (Db2 Codes)00D10A0F (Db2 Codes)00D10A13 (Db2 Codes)00D10A20 (Db2 Codes)

DSNJ382I csect-name CDDS CRITICALPROCESSING FAILED. CDDSSERVICES ARE UNAVAILABLE.

ExplanationAn error occurred during processing of thecompression dictionary data set (CDDS).







https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00d10a0c.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00d10a0d.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00d10a0e.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00d10a0f.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00d10a13.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00d10a20.html

DSNJ383I csect-name CDDS function ERRORFOR DSNAME=dataset-name,ERROR STATUS=mvs-return-code,mvs-reason-code

ExplanationAn error when the specified compression dictionarydata set (CDDS) was opened.


functionThe function that was performed on the CDDS.


mvs-return-codeThe return code issued by the z/OS MVS macro.

mvs-reason-codeThe reason code issued by the z/OS MVS macro.



System programmer responseUse the VSAM OPEN return code and reason codeinformation to resolve the problem.


Related referenceOPEN return and reason codes (DFSMS MacroInstructions for Data Sets)

DSNJ401I csect-name rrrr RECORD NOTFOUND

ExplanationAn attempt was made to read the 'rrrr' record from theBSDS. In so doing, the read routine (DSNJU01B) couldnot find the record.

System actionUtility processing continues. This message is written tothe SYSPRINT data set, not to a console.

DSNJ402I UNABLE TO LOCATE aaaaTBLSPACE NAME IN SYSTEMCATALOG OR DIRECTORYDATABASES

ExplanationThe table space name specified on the TBLSPACEparameter of the change log inventory (DSNJU003)utility SYSTEMDB statement could not be found in anyDb2 subsystem catalog or directory database. Thetable space name in error is named in the 'aaaa'message keyword.

System actionAll subsequent DSNJU003 utility statements arebypassed, and DSNJU003 processing is terminatedwith a return code of 4. The Db2 SYSTEMDB record isnot updated.

This message is written to the SYSPRINT data set, notto a console.

User responseCorrect the table space name specified on theTBLSPACE parameter, and resubmit the change loginventory (DSNJU003) utility job.

DSNJ403I CAPACITY OF BSDS SYSTEMDBRECORD EXCEEDED

ExplanationThe BSDS SYSTEMDB record contains VSAMpasswords for data sets in the Db2 catalog anddirectory, and has a maximum capacity of 168 entries.This message is issued when the number of eligibleDb2 catalog and directory data sets exceeds themaximum capacity of the BSDS SYSTEMDB record.This is an internal error.

System actionAll subsequent change log inventory (DSNJU003)utility statements are bypassed, and DSNJU003processing is terminated with a return code of 4. TheDb2 SYSTEMDB record is not updated.

This message is written to the SYSPRINT data set, notto a console.

User responseNotify the systems programmer.

DSNJ404E keyword NOT ALLOWED FORoperation OPERATION


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/x1cb.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/x1cb.htm

ExplanationAn invalid keyword was used during the operationnamed 'operation'.

System actionThe current utility processing is terminated. Thismessage is written to the SYSPRINT data set, not to aconsole.

User responseCorrect the control statement and rerun the utility.

DSNJ405E keyword1 KEYWORD MUTUALLYEXCLUSIVE WITH keyword2KEYWORD

Explanation'keyword1' and 'keyword2' are mutually exclusive andcannot appear on the same control statement.


User responseDetermine the extraneous keyword and remove it fromthe control statement. Rerun the utility.

DSNJ406E EITHER keyword1 KEYWORD ORkeyword2 KEYWORD MUST BESPECIFIED

ExplanationA required keyword was not used on the controlstatement. Use either 'keyword1' or 'keyword2' withthe attempted control statement type.



DSNJ407I csect-name NO VALIDCHECKPOINT RBA FOUND. LOGWILL BE SCANNED AT RESTART

ExplanationAfter completing its search through the resourcemanager status table and the checkpoint queue, novalid checkpoint RBA was found within the specifiedrange.

System actionUtility processing continues, and will set a return codeof 4. This message is written to the SYSPRINT data set,not to a console.

User responseThe last 100 checkpoints are recorded in the BSDS,including the log STARTRBA and log ENDRBA of thecheckpoint range. When either STARTRBA or ENDRBA/ENDLRSN are specified, the change log inventory(DSNJU003) utility attempts to locate a validcheckpoint in the range. In this case, DSNJU003 wasunsuccessful in finding a valid checkpoint. When Db2is restarted, the log will be scanned to locate thecheckpoint prior to the log truncation point.

DSNJ408I csect-name CHECKPOINT RBAFOUND, RBA = rba, TIME = time

ExplanationAfter completing its search through the resourcemanager status table and the checkpoint queue, 'rba'was the most recent checkpoint RBA in the specifiedrange and 'time' was the time of the checkpoint.

System actionUtility processing continues.

DSNJ409I UNABLE TO WRITE ACTIVE LOGRECORD TO THE BSDS DATASET.DDNAME=xxxxxx

ExplanationA program encountered an I/O error when attemptingto write a BSDS active log record to the BSDS data set.'xxxxxx' is the DDNAME of the BSDS data set beingaccessed.

System actionThe program will terminate.



System programmer responseOne or more error messages describing the specificerror preceded this message. This error is consideredunrecoverable and will leave the BSDS data set in anuncertain state. It will be necessary to either: re-create the data set using access method serviceroutines and then use change log inventory(DSNJU003) to make the active and archive log dataset(s) known to the BSDS, or recover the BSDS using abackup copy.

DSNJ410E csect-name I/O ERROR DURINGoperation-type PROCESSING OFerror-record RECORD

ExplanationAn attempt was made to read, write, or erase a record,but an I/O error occurred.


operation-typeThe type of operation: READ, WRITE, or ERASE.

error-recordThe record that could not be processed:

• Conditional restart control record• Checkpoint queue record• Archive log command history record• Resource manager status table• BSDS member record (BMEM)

System actionThe current utility processing is terminated. MessageDSNJ410E is written to the SYSPRINT data set, and isaccompanied by message DSNJ212I or DSNJ213I.The message is not written to console.

User responseUse the information provided in message DSNJ212I orDSNJ213I to determine the cause of the I/O error.Correct the problem, and resubmit the job.

Related informationDSNJ212Icsect-name ERROR RETURNED FROM BSDSREAD, RPLERRCD=yy, DDNAME=xxxxxxxxDSNJ213Icsect-name ERROR RETURNED FROM BSDSWRITE, RPLERRCD=vsam-code, DDNAME=dd-name

DSNJ411I csect-name CRESTART nnnn FORCRCRID = yyyy, DDNAME =ddname

ExplanationA CRESTART request has just completed. 'nnnn' iseither CREATE or CANCEL. 'yyyy' is the restart controlrecord hexadecimal identifier and 'ddname' is theBSDS data set (SYSUT1 or SYSUT2) associated withthe request.

System actionCurrent utility processing continues. This message iswritten to the SYSPRINT data set, not to a console.

User responseNote the record identifier for future reference.

DSNJ412E csect-name RESTART CONTROLRECORD NOT FOUND IN BSDS

ExplanationThe CRESTART CANCEL keyword was specified but theconditional restart control record does not exist in theBSDS data set.

System actionCurrent utility processing is terminated. This messageis written to the SYSPRINT data set, not to a console.

User responseCREATE the conditional restart control record prior toattempting the CANCEL function.

DSNJ413E csect-name INVALID LOG RANGESCOPE OR CHECKPOINTSPECIFIED

ExplanationThe values specified thru the STARTRBA, ENDRBA,and CHKPTRBA keywords are invalid.

System actionCurrent utility processing is terminated. This messageis written to the SYSPRINT data set, not to a console.

User responseEnsure that the log range values are correct andcorrespond to the other log range values eitherspecified or defaulted. A valid log range is where


STARTRBA is less than or equal to CHKPTRBA, andCHKPTRBA is less than ENDRBA. The STARTRBA mostbe less than or equal to the ENDRBA.

DSNJ414I csect-name COLD START WILLRESULT FROM THIS RESTARTCONTROL RECORD. FORWARDAND BACKOUT SET TO NO.

ExplanationSTARTRBA and ENDRBA are equal. A cold start willresult if this restart control record is used during Db2restart. No forward or backout processing will beperformed.

System actionCRESTART processing continues.

User responseNo additional actions are required if a cold start of thesystem will be performed. If a cold start will not beperformed, reissue the CRESTART and either CANCELthe current restart control record, or CREATE a newrestart control record.

DSNJ415E csect-name ENDRBA = rba ISINVALID, MUST BE A MULTIPLE OF4K

ExplanationThe specified ENDRBA at 'rba' is not a multiple of 4KB.

System actionCRESTART processing is terminated.

User responseCorrect the ENDRBA value on the CRESTARTstatement and rerun the utility.

DSNJ416I WARNING - BSDS UTILITYTIMESTAMP MISMATCHDETECTED. PROCESSINGCONTINUES.

ExplanationAs a result of a change log inventory (DSNJU003)update, it was discovered that the SYSUT1 BSDS andSYSUT2 BSDS timestamps are unequal. Being unequalindicates the possibility of a BSDS mismatch.

System actionCurrent utility processing continues.

User responseRun the print log map (DSNJU004) utility against theSYSUT1 BSDS and SYSUT2 BSDS. Determine if eachBSDS is current. If each BSDS is current, this warningcan be ignored. If either BSDS is not current, deletethe obsolete data set and define a replacement dataset, then copy the current BSDS into the replacementdata set.

DSNJ417I REQUIRED xxxxxxxx PARAMETERFOR yyyyyyyy OPERATION ISMISSING

ExplanationA required parameter 'xxxxxxxx' for a Log utilityoperation was missing from the Log utility controlstatement. The attempted operation is 'yyyyyyyy'.

System actionThe Log utility 'yyyyyyyy' operation does not performits function. All subsequent Log utility controlstatements are processed. A nonzero return code isissued by the utility.


User responseAdd the missing parameter to the control statementsassociated with the specified operation and rerun theutility.

DSNJ418I WARNING - A NOTREUSEABLEACTIVE LOG DATA SET WASDELETED FROM BSDS LOGINVENTORY,STARTRBA=...,ENDRBA=...

ExplanationThe data set name specified on the DSNAMEparameter of the change log inventory (DSNJU003)utility DELETE statement was a NOTREUSABLE activelog.

System actionDSNJU003 processing continues, and will completewith a return code of 4. This message is written to theSYSPRINT data set, not to a console.


User responseNo additional actions are required if a deletion of aNOTREUSABLE active log was intended. Otherwise, re-create the deleted log by using the NEWLOG statementwith the RBA values specified in the warning message.

DSNJ419I UNABLE TO WRITE ARCHIVE LOGRECORD TO THE BSDS DATASET.DDNAME=xxxxxx

ExplanationA program encountered an I/O error when attemptingto write a BSDS archive record to the BSDS data set.'xxxxxx' is the DDNAME of the BSDS data set beingaccessed.

System actionThe program will terminate.


System programmer responseOne or more error messages describing the specificerror preceded this message. This error is consideredunrecoverable and will leave the BSDS data set in anuncertain state. It will be necessary to either: re-create the data set using access method serviceroutines and then use change log inventory(DSNJU003) utility to make the active and archive logdata set(s) known to the BSDS, or recover the BSDSusing a backup copy.

DSNJ420I UNABLE TO WRITE BCR1 RECORDTO BSDS DATASET.DDNAME=xxxxxx

ExplanationA program encountered an I/O error when attemptingto write the BSDS control record to the BSDS data set.'xxxxxx' is the DDNAME of the BSDS data set beingaccessed.



DSNJ421I THE BSDS IS NOT AT THE PROPERRELEASE LEVEL. DDNAME=xxxxx

ExplanationThis message is issued when a program attempting toaccess The BSDS data set is not at a compatiblerelease level. This can be one of the following:

• The program accessing the BSDS data set is at aNEW release level and the BSDS is at the old level.

• The program accessing the BSDS data set is at anOLD release level and the BSDS is at the NEW level.

• The program encountered an UNKNOWN releaselevel on the BSDS data set.

System actionThe program will terminate with no action taken.

System programmer responseIf the program that encountered the error was one ofthe BSDS conversion programs (DSNJMIG0 orDSNJFAL0) an unrecoverable error was found on theBSDS data set and it must be re-created. If the errorwas encountered running some other utility program(i.e., change log inventory or print log map), one of thefollowing actions may be taken:

• Run a version of the program that is compatible withthe release level of the BSDS.

• Run the appropriate formatting program (DSNJMIG0or DSNJFAL0) to convert the BSDS data set to arelease level compatible with the running program. Ifthis was successful, rerun the original program.

DSNJ422I LOG RECORDS HAVE ALREADYBEEN FORMATTED - THIS UTILITYWILL TERMINATE

ExplanationThis message occurs when one of the BSDS formattingprograms detects the BSDS had already beenreformatted or was already at the required formatlevel.

System actionThe program will terminate without any action beingtaken.

System programmer responseIf the appropriate BSDS formatting program was beingrun, no further action is necessary.


DSNJ423I ACTIVE LOG MAY NOT HAVE BEENARCHIVED. DSN=xxxxxx

ExplanationThe program was attempting to convert an old BSDSdata set with more than 31 active log data sets to thenew format. The program will drop the oldest activelog data set(s) to get to the new maximum (31) limit.When dropping one of the old active log data sets fromthe BSDS, it was found to have been flagged as NOTREUSABLE (i.e., this data set MAY NOT have beenarchived). 'xxxxxx' will contain the data set name ofthe active log in question.

System actionThe program will remove this active log data set fromthe BSDS and continue.

System programmer responseCheck to see if this data set had been archived. Theactive log data set was not deleted on disk butremoved only from the BSDS data set, so it may still bearchived, if needed. Use access method serviceroutines to copy the VSAM active log data set to asequential archive log data set.

DSNJ424I csect-name INVALID CONTROLSTATEMENT. THE SECOND WORDMUST BE 'DDNAME' OR '*' ORMUST START WITH APARENTHESIS.

ExplanationThe control statement is invalid.

System actionThe control statement is ignored. Db2 uses theSYSUT1 DD statement to locate the BSDS to bemapped. If the SYSUT1 DD statement is not available,the utility terminates.






DSNJ425I INVALID xxxxxx VALUE/FORMATFOR yyyyyyyy PARAMETER(YYYYDDDHHMMSST)

Explanation'xxxxxx' is the field in the 'yyyyyyyy' parameter thatcontains an incorrect value or incorrect format.



DSNJ426I ENDTIME VALUE CANNOT BE LESSTHAN STARTIME VALUE

ExplanationThe 'STARTIME' and 'ENDTIME' parameters specify atime range. Hence, the ENDTIME value must be equalto or greater than STARTIME value.



DSNJ427I CHECKPOINT RECORD ADDED TOQUEUE

ExplanationThe checkpoint record specified has been added to thecheckpoint queue.







System actionThe BSDS checkpoint queue is modified as stated. Thismessage is written to the SYSPRINT data set, not to aconsole.

DSNJ428I CHECKPOINT RECORD DELETEDFROM QUEUE,STARTRBA=startrba,ENDRBA=endrba

ExplanationThe checkpoint record specified has been deletedfrom the Checkpoint Queue. 'startrba' and 'endrba'was the RBA range indicated in the deleted checkpointrecord.

System actionThe BSDS checkpoint queue is modified as stated. Thismessage is written to the SYSPRINT data set, not to aconsole.

DSNJ429I RBA RANGE CONFLICTS WITHEXISTING CHECKPOINT RECORDRBA RANGE

ExplanationThe specified RBA range for the new checkpoint recordeither exists or overlaps an existing RBA range in thecheckpoint queue.


User responseRun the print log map (DSNJU004) utility against theSYSUT1 BSDS and SYSUT2 BSDS. Determine thecorrect RBA range and correct the STARTRBA andENDRBA parameters and rerun the utility.

DSNJ430I SPECIFIED ENTRY CANNOT BEADDED WITHOUT OVERLAYINGEXISTING LOWEST ENTRY

ExplanationThe specified RBA range for the new checkpoint recordis less than the existing lowest entry. The checkpointqueue is currently full and cannot add the new entrywithout overlaying the lowest entry.


User responseRun the print log map (DSNJU004) utility against theSYSUT1 BSDS and SYSUT2 BSDS. Determine thelowest existing entry and either change the STARTRBAand ENDRBA parameters or delete the existing lowestentry and add the new low checkpoint entry and rerunthe utility.

DSNJ431I STARTRBA SPECIFIED NOTFOUND IN CHECKPOINT QUEUE

ExplanationThe specified STARTRBA could not be located in thecheckpoint queue.


User responseRun the print log map (DSNJU004) utility against theSYSUT1 BSDS and SYSUT2 BSDS. Determine thecorrect STARTRBA value and correct the STARTRBAparameter and rerun the utility.

DSNJ432I THE OFFLRBA VALUE MUST ENDWITH 'FFF'

ExplanationThe OFFLRBA value is invalid. It must end with 'FFF'.



DSNJ433I csect-name INVALID CONTROLSTATEMENT. A MEMBER LISTMUST CONTAIN AT LEAST ONEMEMBER NAME.

ExplanationThe control statement is invalid. The member list iseither empty or in the wrong format.


System actionThe control statement is ignored. Db2 uses theSYSUT1 DD statement to locate the BSDS to bemapped. If the SYSUT1 DD statement is not available,the utility terminates.






DSNJ434I csect-name SYSIN MUST CONTAINAT LEAST ONE RECORD.

ExplanationA SYSIN DD statement was provided, but the data setwas null, or the JCL statement "//SYSIN DD *" wasimmediately followed by the statement "/*".

System actionThe error is ignored. Db2 uses the DD SYSUT1statement to locate the BSDS to be mapped. If theSYSUT1 DD statement is not available, the utilityterminates.






DSNJ435I csect-name THE MEMBER LIST OFA CONTROL STATEMENT MUST BETERMINATED WITH APARENTHESIS.

ExplanationThe control statement contained the correct format forstarting a list of members, but the terminatingparenthesis was not found.

System actionThe control statement is accepted with an assumedparenthesis after the last member name recognized,and processing continues.






DSNJ436I csect-name THE DD STATEMENTFOR ddname IS MISSING.

















ExplanationThe print log map (DSNJU004) utility requestedinformation about the identified ddname from the MVSDynamic Allocation facility, but the DD statement wasnot found in the job.

System actionThe job is terminated.

User responseCorrect the JCL and rerun the job.




Related tasksInvoking stand-alone utilities (Db2 Utilities)Related referenceDSNJU004 (print log map) (Db2 Utilities)

DSNJ437I csect-name UNABLE TO ALLOCATEBSDS dsname. SVC 99 RTN CODErc, RSN CODE rsncd, INFO infocd.

ExplanationThe print log map (DSNJU004) utility attempted toallocate a BSDS data set by using the z/OS DynamicAllocation facility, but the system was unable tocomplete the allocation.


dsnameThe data set name.

rcThe return code from the z/OS DYNALLOC (SVC 99)service.

rsncdThe reason code from the z/OS DYNALLOC (SVC99) service.

infocodeThe information code from the z/OS DYNALLOC(SVC 99) service.

System actionThe processing of the indicated BSDS data set stops. Ifthis data set is the last (or only) BSDS data set to beprocessed by this job, the job is terminated.

User responseSee the reason code information for DYNALLOC todetermine the action to take. Correct the JCL andrerun the job.




.

Related tasksInvoking stand-alone utilities (Db2 Utilities)Related referenceDSNJU004 (print log map) (Db2 Utilities)Interpreting DYNALLOC return codes (MVSProgramming Authorized Assembler ServicesReference)

DSNJ438I csect-name THE xxx VALUE MUSTEND WITH 'yyy'

ExplanationThe STARTRBA or ENDRBA value specified on theNEWLOG statement is invalid. 'xxx' is either STARTRBAor ENDRBA, depending on which parameter is invalid.If 'xxx' equals STARTRBA, then 'yyy' equals '000' and if'xxx' equals ENDRBA, then 'yyy' equals 'FFF'.















DSNJ439I csect_name NEW FUNCTIONMODE REQUIRED FOR xxxxxxOPERATION

ExplanationAn attempt was made to run a log utility requiring new-function mode while Db2 was in conversion mode orenabling-new-function mode.

Db2 must be in new-function mode before the utilityprogram can run successfully. xxxxxx is the name ofthe attempted operation requiring new-function mode.

System actionThe program will terminate with no action taken.

System programmer responseConvert Db2 to new-function mode and retry theprogram.

DSNJ440I BSDS HAS ALREADY BEENCONVERTED, DDNAME=dd-name

ExplanationThis message occurs when a BSDS conversionprogram detects that the BSDS data set that wasspecified by dd-name was already converted.

System actionIf only SYSUT1 was specified, or both SYSUT1 andSYSUT2 data sets were already converted, theprogram terminates with no action taken. In the casewhere both are specified, but only SYSUT1 waspreviously converted, the program continues toprocess the conversion for SYSUT2.

System programmer responseNo further action is necessary.


DSNJ441I INVALID BSDS CONVERSION,DDNAME=dd-name

ExplanationThis message is issued when a program, attempting toaccess the BSDS data set, encounters an invalid BSDS.

An invalid BSDS is the result of a failure during a priorattempt to run a conversion program.

dd-nameThe DDNAME of the BSDS data set being accessed.

System actionThe program terminates with no action taken.

System programmer responseThe procedure for running the program includesmaking a copy of the BSDS before conversion. Restorethe BSDS to the original pre-conversion copy, and trythe conversion again. After the conversion issuccessful, try the program that issued the errormessage again.


DSNJ442I csect-name RECEIVED ERRORSTATUS nnn FROM macro-name

ExplanationDb2 encountered an error while issuing macro macro-name. Error status is the return code from thespecified macro.

System actionThe requested operation fails.

User responseIf the error is from the CONVTOD macro, ensure thatthe ENDTIME timestamp value is valid and in thecorrect format.

DSNJ443I csect-name ENDTIME LOGTRUNCATION POINT =xxxxxxxxxxxx

ExplanationThe ENDTIME timestamp value results in a logtruncation at LRSN or STCK value xxxxxxxxxxxx.

System actionUtility processing continues.

DSNJ444I csect-name ENDTIME TIMESTAMPIS GREATER THAN THE CURRENTTIMESTAMP






ExplanationThe ENDTIME timestamp must be a system time-of-day clock timestamp for which there exists a logrecord with a timestamp that is greater than, or equalto, the specified timestamp value.

System actionThe utility terminates.

User responseSpecify an ENDTIME timestamp value that is valid forlog truncation.

DSNJ445I action-type REQUEST FAILED:error-description

ExplanationA DSNJU003 (change log inventory) utility operationfailed.

action-typeThe DSNJU003 operation: DELMBR or RSTMBR.

error-descriptionA description of the error that occurred:CRESTART FAILED: SYSPITR LRSN MUST BEGREATER THAN minimum-value OF LASTMEMBER DESTRUCTION

An attempt was made to use a CRESTARTstatement to create a conditional restartrecord for system point in time recovery.However, the CRESTART statement specified alog truncation point LRSN that is before themost recent member destruction. The logs ofthe destroyed member are no longer available.The minimum LRSN value is indicated in themessage as minimum-value.User response

Specify an LRSN that is greater than theminimum value indicated in the message.

CRESTART FAILED: SYSPITRT TIMESTAMP MUSTBE GREATER THAN minimum-value OF LASTMEMBER DESTRUCTION

An attempt was made to use a CRESTARTstatement to create a conditional restartrecord for system point in time recovery.However, the CRESTART statement specified alog truncation point time stamp that is beforethe most recent member destruction. The logsof the destroyed member are no longeravailable. The minimum time stamp value isindicated in the message as minimum-value.

User responseSpecify a time stamp that is more recentthan the minimum value indicated in themessage.

DEACTIV ON A MEMBER ALREADYDEACTIVATED

DELMBR DEACTIV was requested for amember that has already completeddeactivation processing.

DEACTIV ON A MEMBER ALREADY DESTROYEDDELMBR DEACTIV was requested for amember that has already completeddestruction processing.

DEACTIV ON A MEMBER ALREADY MARKED FORDEACTIVATION

DELMBR DEACTIV was requested for amember that has already been marked fordeactivation, but the deactivation process hasnot yet completed.System action

The state of the member is unchanged.DEACTIV ON A MEMBER ALREADY MARKED FORDESTRUCTION

DELMBR DEACTIV was requested for amember that has already been marked fordestruction by a previous DESTROY request.

DEACTIV ON A NON-EXISTENT MEMBER INNON-DATA SHARING

An attempt was made to deactivate a memberfrom the BSDS of a non-data sharing Db2subsystem. Deactivation is allowed in datasharing mode only.User response

Verify the member ID.DESTROY ON A MEMBER ALREADY DESTROYED

DELMBR DESTROY was requested for amember that has already completeddestruction processing.

DESTROY ON A MEMBER ALREADY MARKED FORDESTRUCTION

DELMBR DESTROY was requested for amember that has already been marked fordestruction but the destruction process hasnot yet completed.System action

The state of the member is unchanged.DESTROY ON A NON-EXISTENT MEMBER INNON-DATA SHARING

An attempt was made to destroy a memberfrom the BSDS of a non-data sharing Db2subsystem. Destruction is allowed in datasharing mode only.


User responseVerify the member ID.

INVALID AFTER A NON-DELMBR OR NON-RSTMBR OPERATION

A control statement other than DELMBR orRSTMBR preceded the current DELMBR orRSTMBR statement. The statement is notallowed if the BSDS being processed belongsto the target member. The DELMBR or RSTMBRstatement is not processed.User response

Restart the member that owns the BSDS sothat previous changes to the BSDS can beprocessed.

INVALID AFTER DELMBR OR RSTMBROPERATION

A control statement other than DELMBR orRSTMBR was issued for a data sharing groupmember that is queued for deletion. WhenDELMBR or RSTMBR is input to DSNJU003, noother operations are allowed if the BSDS that isbeing processed belongs to the target member.System action

The other control statements are notprocessed. If the BSDS that belongs to thetarget member is marked as deactivated ordestroyed by a previous invocation, nofurther updates to the BSDS are allowed.The exception is if the target member wasdeactivated and an RSTMBR operation isrequested.

INVALID WITH HOST MEMBER IN DEACTIV/DESTROY STATE

A control statement other than RSTMBR wasissued for a data sharing group member thathas been deactivated. When a data sharinggroup member has been deactivated, the onlycontrol statement that DSNJU003 accepts forthat member's BSDS is RSTMBR. When amember is marked as destroyed in its ownBSDS, DSNJU003 rejects all statements thatwould alter the BSDS contents.

MEMBER ALREADY DESTROYEDRSTMBR was requested for a member that wasdestroyed. RSTMBR can be used only when amember is deactivated or marked fordeactivation.

MEMBER ALREADY MARKED FOR DESTRUCTIONRSTMBR was requested for a member that wasmarked for destruction but not yet completelydestroyed. RSTMBR can be used only when amember is deactivated or marked fordeactivation.

User responseIf a backup copy of the BSDS is availablefrom before DELMBR DESTROY was used,restore the backup.

MEMBER HAS NOT BEEN DEACTIVATEDEither RSTMBR or DELMBR DESTROY wasrequested for a member that is not deactivatedor marked for deactivation. A DELMBRDESTROY can immediately follow a DELMBRDEACTIV for the same member ID, but aDELMBR DEACTIV is always required first.User response

Either complete the deactivation processor use DELMBR DEACTIV followed byDELMBR DESTROY for the target member.

MEMBER HAS NOT BEEN QUIESCEDDELMBR was requested for a member that hasnot been quiesced or was active when themember that owns the BSDS was shut down. Amember must be quiesced before a DELMBRcommand will be accepted.User response

Quiesce the target member. To update thestate of the target member, restart themember that owns the BSDS thatDSNJU003 was running against.

NON-EXISTENT MEMBER IN NON-DATASHARING

RSTMBR was requested for a nonexistentmember and the BSDS indicates the memberthat owns the BSDS is not part of a datasharing group. In a non-data sharingenvironment, RSTMBR can be used only for aknown member that has been marked fordeactivation through the DELMBR DEACTIVstatement.User response

Indicate a different member number.UTILITY TIMESTAMP GREATER THAN SYSTEMTIMESTAMP. MEMBER RESTART REQUIRED.

DELMBR was requested, but failed because anearlier change to the BSDS updated the utilitytime stamp. The member must be restartedbefore DELMBR can be used.User response

Restart the member that owns the BSDSbefore using DELMBR DEACTIV.

VALID MEMBER ID IS 1 TO 32 DECIMALAn invalid member ID was specified. The validrange is 1 to 32, inclusive.User response

Specify a member ID between 1 and 32.


System actionThe change log inventory utility terminates. MessageDSNJ445I is written to the SYSPRINT data set.

Additional actions occur for some error-descriptionvalues, and are described under System actionin theexplanation of the value.

User responseTake the action indicated under User response for theerror-description value.

Related referenceDSNJU003 (change log inventory) (Db2 Utilities)

DSNJ446I operation-type SUCCESSFUL FORMEMBER ID member-id, MEMBERNAME member-name

ExplanationThe change log inventory utility (DSNJU003)successfully completed a DELMBR or RSTMBRrequest.

operation-typeThe type of operation: DELMBR DEACTIV, DELMBRDESTROY, or RSTMBR

member-idThe ID number of the member that was the targetof the request.

member-nameThe name of the member that was the target of therequest.

System actionProcessing completes. Message DSNJ446I is writtento the SYSPRINT data set.



DSNJ447I KEYWORD required-keyword ISREQUIRED WHEN KEYWORDspecified-keyword IS SPECIFIED

ExplanationA change log inventory utility (DSNJU003) controlstatement specified a keyword that requires anadditional keyword that was not specified.

required-keywordThe name of the keyword that is required whenspecified-keyword is used.

specified-keywordThe name of the keyword that was specified. Thiskeyword cannot be used without required-keyword.

System actionThe statement is ignored. The utility terminates withRC=4. Message DSNJ447I is written to the SYSPRINTdata set.

User responseCorrect the syntax of the control statement, andresubmit the utility job.


DSNJ448I ERROR DURING BSDSCONVERSION. error-condition

ExplanationAn error occurred during BSDS format conversion.

error-conditionText that describes the error that occurred.OUTPUT BSDS CI SIZE NOT CORRECT,DDNAME=dd-name

The CI size of the output BSDS should be8192.dd-name

The JCL DD name of the data set with theincorrect CI size. Delete and redefine theoutput BSDS.

log-type LOG DATA SET dataset-name HAS ANASSOCIATED PASSWORD

Db2 does not support active or archive log datasets with passwords defined.log-type

Indicates whether an active log or archivelog data set has a password.

dataset-nameThe name of the data set with thepassword.

INPUT BSDS NOT IN CORRECT FORMAT,DDNAME=dd-name

dd-nameSpecifies the data set that was not in theformat that supports 93 active logs and10,000 archive logs. If you have not yet run





DSNJCNVB against the BSDS, runDSNJCNVB first and then run DSNJCNVT.

INPUT AND OUTPUT BSDS ARE THE SAME.INPUT=input-name, OUTPUT=output-name

The converted BSDS cannot be the same as theBSDS to be converted.input-name

The JCL input name of the data set.output-name

The JCL output name of the data set.UNRECOGNIZED BSDS RECORD, KEY=key-value

During conversion of the BSDS, a record wasfound that is not a known format.key-value

The VSAM KSDS key of the BSDS recordthat was not recognized. To determine theoperation that inserted the record into theBSDS, use IDCAMS PRINT and specify thiskey value. If the record is not needed,delete it and rerun the BSDS conversion

RETURN CODE return-code, REASON CODEreason-code

An error condition was found. For moreinformation, see the reason code explanation.

System actionThe program terminates. The output BSDS is notusable. The input BSDS is unaltered.

Programmer response:Correct the error condition and rerun the conversionprogram.

Related referenceDSNJCNVT (Db2 Utilities)

DSNJ700I csect_name ERROR ATTEMPTINGTO ACCESS BSDS FOR member-type MEMBER ID= member-id,MEMBER NAME= member-name,REASON-CODE= reason-code.

ExplanationDb2 issues this message to identify the peer or proxymember ID, and if known, the peer or proxy membername that are associated with the listed Db2 reasoncode.

member-typeOne of the following values:PEER

The BSDS is for a member of the same datasharing group.

PROXYThe BSDS is for a member of a proxy datasharing group in a GDPS ContinuousAvailability with zero data loss environment.

member-idThe IRLM member identifier for the member of thedata sharing group.

member-nameThe member name of the Db2 data sharingmember that is not in this data sharing group.


System actionAn execution unit issues this message and then, if thiswas an unconditional request, writes a record toSYS1.LOGREC and requests an SVC dump. Theexecution unit then terminates.

Operator responseCollect all relevant diagnostic materials, includingSYS1.LOGREC, SVC dump, and console output of peerand host.

System programmer responseReview the explanation for the associated Db2 reasoncode for further action.

DSNJ701E csect-name MEMBER NAME(membername) IN BSDS DOES NOTMATCH MEMBER NAME(membername) IN DB2 SYSTEMPARAMETERS dsnzparm

ExplanationDuring startup, Db2 detected that the member namelisted in its bootstrap data set (BSDS) does not matchthe member name in the Db2 system parameters loadmodule.


System programmer responseRestore the BSDS or specify a different systemparameters load module on the START DB2 command.

DSNJ702E csect_name GENERIC LU NAME lu-name IN BSDS DOES NOT MATCHTHE GENERIC LU NAME lu-name




ASSOCIATED WITH THE DATASHARING GROUP.

ExplanationDb2 issues this message during startup when itdetects that the generic LU name in the bootstrap dataset (BSDS) does not match the generic LU name in theshared communications area (SCA) structure.




System programmer responseDepending on the accuracy of the BSDS value, takeone of the following actions:

• BSDS value is correct: Db2 startup will automaticallyreplace the generic LU name in the SCA with thecorrect value. The BSDS for each member of this Db2data sharing group must specify this same value forgeneric LU name.If any member specifies a differentvalue for generic LU name, use the change loginventory utility (DSNJU003) to change the genericLU name.

• BSDS value is not correct: Db2 startup will replacethe generic LU name in the SCA. The SCA value willbe incorrect when startup is complete. Take thefollowing actions to correct this situation:

– Stop this Db2 subsystem.– Use the change log inventory utility (DSNJU003)

to change the generic LU name of this member.– Issue START DB2 for this member. START DB2 will

correct the generic LU name contained in the SCA.


DSNJ703E csect-name GROUP NAME(groupname) IN BSDS DOES NOTMATCH GROUP NAME (groupname)IN DB2 SYSTEM PARAMETERSdsnzparm

ExplanationDuring startup, Db2 detected that the group namelisted in its bootstrap data set (BSDS) does not match

the group name in the Db2 system parameters loadmodule.


System programmer responseRestore the BSDS or specify a different systemparameters load module on the START DB2 command.

DSNJ704I csect-name NEWMEMBER(member-name) START-UP NOT ALLOWED WHEN GROUP-RESTART IS REQUIRED FORGROUP(group-name).

ExplanationOne of the following occurred:

• A new member member-name tried to start when agroup restart of data sharing group group-name isrequired.

• A member other than the originating member of adata sharing group attempted to start the new Db2data sharing group. The originating member of agroup is either an existing Db2 subsystem whichformed the data sharing group or a new Db2subsystem which was installed to form the group.

System actionThe Db2 subsystem stops.

Operator responseStart a previously active member of this group. Whenthe required group restart is completed, start the newmember again.

If this is the very first startup of the group, you muststart the originating member first before starting anyother member.

DSNJ705I csect-name THE DB2 SYSTEMPARAMETERS SPECIFY DATASHARING, BUT THE BSDSSPECIFIES NON-DATA SHARING.

ExplanationThe system parameters passed on the Db2 startcommand specified data sharing, but the bootstrapdata set (BSDS) did not indicate this Db2 is a datasharing member.




Operator responseIf this Db2 should be a member of a data sharinggroup, inform the system programmer. If this Db2 isnot a member of a data sharing group, restart Db2 withthe correct system parameters load module

System programmer responseIf this Db2 should be a member of a data sharinggroup, execute the installation job DSNTIJUZ, whichupdates the BSDS for data sharing.

If this Db2 is not a member of a data sharing group,reassemble the system parameters load module andspecify DSHARE=NO.

If this Db2 is attempting to disable the data sharinggroup, then reassemble the system parameters loadmodule and specify DSHARE=NO, then execute theinstallation job DSNTIJGF, and then restart this Db2.Job DSNTIJGF must be used with caution, this willdisable the data sharing group.

Related tasksDisabling data sharing (Db2 Installation andMigration)Migration step 11: Define Db2 initializationparameters: DSNTIJUZ (Db2 Installation andMigration)Installation step 5: Define Db2 initializationparameters: DSNTIJUZ (Db2 Installation andMigration)Related referenceDATA SHARING field (DSHARE subsystemparameter) (Db2 Installation and Migration)

DSNJ706I csect-name THE DB2 SYSTEMPARAMETERS SPECIFY NON-DATASHARING, BUT THE BSDSSPECIFIES DATA SHARING.

ExplanationThe system parameters passed on the DB2 STARTcommand specified non-data sharing, but thebootstrap data set (BSDS) indicates this is a datasharing member.


Operator responseIf this Db2 is a member of a data sharing group, restartDb2 with the correct system parameters load module.If this Db2 is not a member of a data sharing group,inform the system programmer.

System programmer responseIf this Db2 should be a member of a data sharinggroup, reassemble the system parameters loadmodule and specify DSHARE=YES. If this Db2 is not amember of a data sharing group, execute theinstallation job DSNTIJGF, which updates the BSDS fornon-data sharing.

DSNJ707E csect_name LOCATION NAMElocation-name IN BSDS DOES NOTMATCH THE LOCATION NAMElocation-name ASSOCIATED WITHTHE DATA SHARING GROUP.

ExplanationDb2 issues this message during startup when itdetects that the LOCATION name in the bootstrap dataset (BSDS) does not match the LOCATION name in thesystem communications area (SCA) structure.




System programmer responseDepending on the accuracy of the BSDS value, takeone of the following actions:

• BSDS value is correct: Db2 startup will automaticallyreplace the LOCATION name in the SCA with thecorrect value. The BSDS for each member of this Db2data sharing group must specify this same value forLOCATION. If any member specifies a different valuefor LOCATION, use the change log inventory utility(DSNJU003) to change the LOCATION name.

• BSDS value is not correct: Db2 startup will replacethe LOCATION name in the SCA. The SCA value willbe incorrect when startup is complete. Take thefollowing actions to correct this situation:

– Stop this Db2 subsystem.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_procdisabledshare.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_procdisabledshare.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntijuzmigr.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntijuz.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_dshare.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_dshare.html

– If any member specifies a different value forLOCATION, use the change log inventory utility(DSNJU003) to change the LOCATION name.

– Issue START DB2 for this member. START DB2 willcorrect the LOCATION name contained in the SCA.

Related conceptsUpdate the BSDS with the DSNJU003 utility(Db2 Data Sharing Planning and Administration)Related referenceDSNJU003 (change log inventory) (Db2 Utilities)

DSNJ708I csect-name NEW MEMBER START-UP IS NOT ALLOWED WHEN THEDATA SHARING GROUP IS INSYSTEM RECOVER PENDINGMODE

ExplanationA new data sharing member attempted to join the datasharing group when the data sharing group is inSystem Recover Pending mode.


Operator responseWhen the data sharing group is no longer in SystemRecover Pending mode, start the new member again.

DSNJ709I csect-name RBA/LRSN value WILLBE NEAR THE END OF THE LOGRANGE. REPLY Y TO CONTINUE, NTO CANCEL

ExplanationThis message is issued during enable, disable, or re-enable of data sharing mode if the resulting RBA orLRSN value is close enough to the end of the log rangethat normal SQL processing is not allowed.


RBA/LRSNIf you are disabling data sharing, the string RBA isdisplayed. Otherwise, the string LRSN is displayed.

valueThe value of the RBA or LRSN if the operationcontinues.

System actionIf Y is entered, the operation proceeds. If N is entered,the restart is terminated.

Operator responseConsult with the system programmer or databaseadministrator to determine the correct reply.

System programmer responseDetermine whether the RBA or LRSN value isacceptable. When the RBA or LRSN log is nearing theend of the RBA or LRSN range, normal SQL updates failwith resource unavailable errors for objects that are inbasic 6-byte format. Convert database objects toextended 10-byte format before the end of the logrange is reached.

DSNJ711E csect-name SCA OPEN FAILUREENCOUNTERED.

ExplanationA failure occurred during command processing in anattempt to open an object in the SCA.

System actionCommand processing terminates unsuccessfully.

System programmer responseObtain SYS1.LOGREC and possible SVC dump foranalysis.

Problem determinationReview the Db2 system console for possible DSN7xxxxand/or SVC dump messages that could relate to thisproblem.


DSNJ712E csect-name SCA READ FAILUREENCOUNTERED.

ExplanationA failure occurred during command processingattempting to read from the SCA.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_updatebsdsdsnju003.html








DSNJ713E csect-name SCA WRITE FAILUREENCOUNTERED.

ExplanationA failure occurred during command processingattempting to write to the SCA.





DSNJ990I csect-name SHOWCB ERROR,DDNAME = dd-name RETURNCODE = error-code REASON CODE= reason-code

ExplanationThe VSAM macro SHOWCB failed when it wasprocessing the specified data set.


error-codeThe error code. A value of 4 means that the logdata set was allocated as greater than 4 GB in size,which is not supported.

reason-codeThe reason code.

dd-nameThe DD name for the data set that SHOWCB wasprocessing when it failed.


System programmer responseSee the information about macro return and reasoncodes for SHOWCB at Control block manipulationmacro return and reason codes ( z/OS DFSMStvsAdministration Guide ).

If the log data set was allocated as greater than 4 GBin size, reallocate the data set to be less than 4 GB insize.


Severity8 (error)

Related referenceVSAM macro descriptions and examples(DFSMS Macro Instructions for Data Sets)

DSNJ991I csect-name START OF LOG DATASET PREFORMAT FOR JOB job-name step-name

ExplanationThe active log data set preformat utility has started.


DSNJ992I csect-name DDNAME = dd-nameLOG DATA SET NAME = data-set-name

ExplanationThe indicated data-set-name is to be preformatted.






http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idat300/x1i.htm





The DDNAME dd-name was used to process the dataset. This message is issued multiple times if multipleactive log data sets are being preformatted.


DSNJ993I csect-name LOG DATA SET IS NOTA VSAM DATA SET

ExplanationThe input log data set is not a VSAM data set.


User responseUse the AMS IDCAMS Service to define the active logdata set as a VSAM Linear data set.

Severity8 (error)

DSNJ994I csect-name VSAM OPEN ERROR,DDNAME = dd-name ACBERRFLG =error-code

ExplanationVSAM OPEN failed with the indicated ACB error-codefor the indicated dd-name.

System actionProcessing terminates if the error code is greater thanor equal to 128; otherwise, processing continuesnormally.

System programmer responseFollow standard VSAM diagnostic procedure. Refer toz/OS DFSMS: Macro Instructions for Data Sets.


Severity8 (error) if error is greater than or equal to 128;otherwise, 4 (warning)

DSNJ995I csect-name VSAM PUT ERROR,DDNAME = dd-name, RPLERREG =

return-code, RPLERRCD = reason-code

ExplanationVSAM PUT failed with the indicated return-code andreason-code for the listed dd-name.


System programmer responseFollow standard VSAM diagnostic procedure. Refer toz/OS DFSMS: Macro Instructions for Data Sets.

User responseNotify system programmer.

Severity8 (error)

DSNJ996I csect-name LOG PREFORMATCOMPLETED SUCCESSFULLY,nnRECORDS FORMATTED FORDDNAME dd-name

ExplanationThe active log data set was preformatted successfully.nnrecords (or VSAM control intervals) were formattedfor the indicated dd-name. Multiple messages areissued if multiple log data sets are being preformattedconcurrently.


DSNJ997I csect-name LOG PREFORMATTERMINATED

ExplanationPreformatting of the active log data set did notcomplete successfully.


User responseExamine other error messages associated with thisjob.


Severity8 (error)

DSNJ998I csect-name LOG DATA SET IS NOTEMPTY, DDNAME = dd-name

ExplanationThe input log data set that is designated by dd-name isnot an empty data set. The input data set must beempty to prevent the loss of actual log data.


User responseUse the AMS IDCAMS Service to delete and redefinethe active log data set or correct the input log data setname.

Severity8 (error)


Chapter 9. DSNL messagesMessage identifiers that begin with DSNL communicate information about the distributed data facility.

DSNL001I DDF IS ALREADY STARTED

ExplanationThe distributed data facility (DDF) was already activewhen you issued -START DDF command.

System actionThe issued command is not executed.

DSNL002I DDF IS ALREADY STOPPED

ExplanationThe distributed data facility (DDF) had already beenstopped when the -STOP DDF command was issued.


DSNL003I DDF IS STARTING

ExplanationThe distributed data facility (DDF) -START command isstarting.

System actionDb2 begins processing the -START DDF command.

DSNL004I csect-name DDF START COMPLETELOCATION location-name LUnetwork-name.luname GENERICLUnetwork-name.generic-lunameDOMAIN domain-name TCPPORTincoming-port SECPORT secure-port RESPORT resynch-portIPNAME ip-name OPTIONS:PKGREL = pkgrel-value

ExplanationThe distributed data facility (DDF) started.


location-nameThe location of the Db2 subsystem.

network-name.lunameThe fully qualified LU name for the Db2 subsystem.

The value '- NONE' indicates that the Db2subsystem has not activated its SNA/APPCcommunications support.

network-name.generic-lunameThe fully qualified VTAM generic LU name for theDb2 subsystem.

The value '-NONE' indicates that no VTAM genericLU name was defined to be used by the Db2subsystem or that SNA was not activated.

domain-name

For non-data sharing systems, the member-specific domain name that maps to the member-specific IP address.

For data sharing systems, the group domain namethat maps to the group IP address.

The domain name can be specified in the DNS or alocal host file.

The value '-NONE' indicates that TCP/IP is notsupported, TCP/IP initialization failed, or Db2 hasbeen started in restricted access mode.

incoming-portThe TCP/IP port number that is used by this Db2subsystem to accept incoming DRDA connectionrequests.

• A value of 0 indicates that TCP/IP is notsupported. The BSDS DDF record is notconfigured with a PORT.

• A value of '-NONE' indicates that Db2 will notaccept connections on this port. This conditioncan be caused by a value of 0 for the MAXDBATsubsystem parameter.

secure-portThe TCP/IP port number that is used by this Db2subsystem to accept incoming secure DRDAconnection requests.

A value of 0 indicates that the BSDS DDF record isnot configured with a SECPORT.

resynch-portThe TCP/IP port number that is used by this Db2subsystem to accept incoming two-phase commitresynchronization requests.

A value of 0 indicates that TCP/IP is not supported.The BSDS DDF record is not configured with aRESPORT.


ip-nameThe name given to this Db2 subsystem for use asthe network ID portion of the unit of workidentifier.

• A value of '-NONE' indicates that either the BSDSDDF record does not have a value for IPNAME

• Any other value indicates that DDF has activatedTCP/IP communications support in such a waythat the value of network-name.luname will be '-NONE'.

pkgrel-valueThe current value of the DDF PKGREL processingoption. Possible values are:BNDOPT

When a connection which has used a highperformance DBAT terminates, the highperformance DBAT is also be deallocated.

BNDPOOLDDF processing is the same as for the BNDOPToption, with the following exception. When aconnection that was used for a highperformance DBAT terminates, the highperformance DBAT is pooled. The pooled DBATcan then be used by another connection thatpresents a request to the subsystem.

COMMITPackages are always allocated underRELEASE(COMMIT) rules regardless of theirpackage RELEASE bind option value.

When an access thread has completed a unit ofwork, and the DBAT can be pooled, DDF poolsthe DBAT, makes an accounting record, deletesthe current WLM enclave, and inactivates theconnection. Pooled access threads release allpackage allocation locks.

If the CMTSTAT subsystem parameter is set toACTIVE, then the message will always indicatethat PKGREL IS SET TO COMMIT, regardless ofthe value specified on the command.

System actionThe DDF start up process completed. However, itmight fail for reasons specified by messagesDSNL013I, DSNL015I, DSNL016I, DSNL017I,DSNL018I, DSNL019I, DSNL700I, or DSNL705I.

System programmer responseUse the recommended domain name to configurenetwork definitions for TCP/IP requesters.

Related conceptsDistributed data facility (Introduction to Db2 forz/OS)

Related tasksStarting DDF (Db2 Administration Guide)Related referenceMAX REMOTE ACTIVE field (MAXDBATsubsystem parameter) (Db2 Installation andMigration)RELEASE bind option (Db2 Commands)-START DDF (Db2) (Db2 Commands)

DSNL005I DDF IS STOPPING

ExplanationThe distributed data facility (DDF) -STOP commandhas been initiated.

System actionThe -STOP DDF command is initiated.

DSNL006I DDF STOP COMPLETE

ExplanationThe distributed data facility (DDF) -STOP commandhas completed.

System actionThe DDF has stopped.

DSNL007I DDF IS ABNORMALLYTERMINATING

ExplanationAbnormal termination of the distributed data facility(DDF) has started.

System actionAbnormal termination of the DDF is starting.

DSNL008I DDF ABNORMAL TERMINATIONCOMPLETE

ExplanationAbnormal termination of the distributed data facility(DDF) has completed.

System actionThe DDF has stopped.

DSNL009I INVALID DDF THREAD logical-unit-of-work-id SPECIFIED


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_distributeddatafacility.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_distributeddatafacility.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_startddf.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_maxdbat.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptrelease.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_startddf.html

ExplanationNo distributed transaction with the specified 'logical-unit-of-work-id' exists.

System actionThe specified thread is not canceled.

User responseDetermine the correct 'logical-unit-of-work-id' of thedistributed thread that is to be canceled and thenreissue the command.

Problem determinationDetermine the correct value. The -DISPLAY THREADcommand can be used to display all distributedactivity.

DSNL010I DDF THREAD luw-id HAS BEENCANCELED

ExplanationThe distributed data facility (DDF) thread with thespecified logical unit of work ID was canceled.

luw-idThe logical unit of work ID.

In the following cases, more than one DDF threadmight be canceled:

• If the logical unit of work ID is an LU network nameand an LUW instance number, instead of an LUWIDtoken, and an application accesses the same Db2server by different access paths (for example, A->B->C and A->D->C). In this case, multiple threads withthe same LUWID exist at the server (for example, C).If CANCEL DDF THREAD is issued at the server,specifying this LUWID, every thread at the serverwith the LUWID is canceled. This case occurs rarely.

• If the logical unit of work ID is an LUWID token, andmultiple server threads have the same logical unit ofwork ID. This happens when threads are processingsecondary connections in support of an applicationthat uses package-based continuous block fetch. Allserver threads that are associated with thesecondary connections are canceled.

System actionThe specified thread is canceled.

DSNL011I VTAM STOPPING DDF

ExplanationThe operator issued a HALT NET command toterminate VTAM.

System actionThe distributed data facility (DDF) -STOP command isinitiated.

DSNL012I VTAM TERMINATING DDF

ExplanationThe operator issued a HALT NET QUICK command or aHALT NET CANCEL command, or VTAM is terminatingabnormally. This message can be issued any time after-START DDF and occurs when VTAM is stopped, whichcan occur prior to DDF termination. This message isnot issued when DDF terminates normally.

System actionTermination of the distributed data facility is initiated.

DSNL013I VTAM OPEN ACB FAILEDERROR=error-code

ExplanationVTAM returned a nonzero return code after Db2invoked the OPEN ACB macro instruction duringtermination of the distributed data facility (DDF). VTAMreturn codes for OPEN error conditions are defined inz/OS Communications Server SNA Programming.

System actionTermination of the distributed data facility is initiated.


System programmer responseDetermine the cause of the OPEN ACB failure, correctthe error, and issue the -START DDF command.

Problem determinationFor relevant diagnostic information, see OPENmacroinstruction error fields(z/OS CommunicationsServer: IP and SNA Codes).

DSNL014I VTAM CLOSE ACB FAILEDERROR=error-code

Chapter 9. DSNL messages 331

http://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.cs3cod0/acbopen.htm



ExplanationVTAM returned a nonzero return code after Db2invoked the CLOSE ACB macro instruction duringtermination of the distributed data facility (DDF). VTAMreturn codes for CLOSE error conditions are defined inz/OS Communications Server SNA Programming.

System actionTermination of DDF continues.


System programmer responseDetermine the cause of the failure, fix the errorcondition, and then issue the -START DDF command.

Problem determinationRefer to z/OS Communications Server SNAProgramming for failure analysis during a CLOSE macroinstruction.

DSNL015I VTAM SETLOGON FAILEDRTNCD=error-code FDBK2=open-flags

ExplanationVTAM returned a nonzero return code after Db2invoked the SETLOGON macro during initialization ofthe distributed data function (DDF). VTAM return codesare defined in z/OS Communications Server SNAProgramming.

System actionTermination of the DDF is started.


System programmer responseRefer to z/OS Communications Server SNAProgramming to determine the cause of the failure.After the error is fixed, issue the -START DDFcommand.

DSNL016I DDF RECORD NOT FOUND IN BSDS

ExplanationDDF cannot find the DDF communication record in theBSDS.

System actionDDF termination process is initiated.


System programmer responseUse the change log inventory to add the DDFcommunication record to the BSDS.

Problem determinationCollect the following diagnostic item:

• Print the contents of the BSDS using the print logmap utility.

DSNL017I INVALID DDF RECORD FOUND INBSDS REASON = reason-code

ExplanationAn invalid or incomplete DDF communication recordwas found in the BSDS.

System actionDDF begins to terminate processing.


System programmer responseSee the information for the associated reason-code.Use the change log inventory utility to correct the DDFcommunication record in the BSDS.

Problem determinationCollect the following diagnostic item:

• Print the contents of the BSDS using the print logmap utility.

DSNL018I VSAM ERROR READING DDFRECORD IN BSDSRPLERRCD=error-code


ExplanationA VSAM GET command was issued that resulted in anonzero return code. RPLERRCD 'error-code' is theVSAM return code.

System actionTermination of the distributed data facility (DDF) isinitiated.


System programmer responseDetermine the cause of the failure, fix the errorcondition, and issue the -START DDF command.

The cause of the failure is dictated by the VSAM returncode. The BSDS may have to be recovered by using abackup copy.

Problem determinationRefer to the appropriate VSAM publications.

DSNL019I VTAM DOES NOT SUPPORT APPCFUNCTIONS

ExplanationThe installed release of VTAM does not support theadvanced program-to-program communications(APPC) application program interface (API). The APPCAPI bit is not set in the VTAM function-list vector in theaccess-method-support vector list.



System programmer responseDetermine whether the installed release of VTAMsupports the APPC API. If VTAM does not support theAPPC API, a VTAM release that supports the APPC APImust be installed before the DDF can be started.

DSNL020I KEYWORD 'THREAD' PARAMETER'parameter' FORMAT IN ERROR

ExplanationThe parameter value specified for the logical unit ofwork ID on the CANCEL DDF THREAD has an invalidformat.

parameterThe invalid parameter string.

The correct format for the parameter is eithernetwork-id.luname.luwunique orluname.luwunique, using the following values:

network-idAn optional 1- to 8-character network ID.

lunameA 1- to 8-character logical unit name.

luwuniqueA 12-character hexadecimal number.


User responseDetermine the correct logical unit of work ID of thedistributed thread that is to be canceled and reissuethe command.

Problem determinationUse the -DISPLAY THREAD command to display alldistributed activity.

DSNL021I command ACCEPTED

ExplanationThe 'command' command has been accepted andasynchronous processing of 'command' has beeninitiated. The command can only be -START or -STOPthe distributed data facility.

System actionThe command was accepted and asynchronousprocessing has been initiated.

DSNL022I csect-name DDF THREAD 'luw-id'WAS PREVIOUSLY CANCELED

ExplanationA command to cancel the distributed data facility(DDF) thread luw-id was issued, but a command tocancel the same thread has already been issued.



luw-idThe logical unit of work ID.

Either the CANCEL DDF THREAD or the CANCELTHREAD command was entered.

System actionThe thread is currently being canceled.


Programmer responseThe CANCEL command terminates a thread only if thethread is processing in Db2 or is currently suspendedby Db2. The thread might not be processing in Db2 inthese situations:

• The thread is processing in the application and hasnot made a request to Db2. The DISPLAY THREADcommand indicates this.

• The user placed the thread on an MVS resourceusing the ENQUE command. The CANCEL commandhas no effect on the thread until ENQUE completesand the thread returns to Db2.

• The thread is processing in VTAM and is waiting for aresponse from a partner. The DISPLAY THREADDETAIL command indicates this. In this case thethread does not terminate until VTAM returns to Db2.VTAM commands, which will terminate the sessionor LU, can be used to cause VTAM to return to Db2.

DSNL023I DDF IS ALREADY IN THE PROCESSOF STARTING

ExplanationThe distributed data facility (DDF) was starting whenthe -START DDF or -STOP DDF command was issued.


DSNL024I DDF IS ALREADY IN THE PROCESSOF STOPPING

ExplanationThe distributed data facility (DDF) was stopping whenthe -STOP DDF or -START DDF command was issued.

System actionThe -START or -STOP DDF command is not executed.

DSNL025I A DISTRIBUTED AGENT FOR luw-id=token EXISTS AT THISLOCATION BUT NOT AT SITE WITHLOCATION location AND LU luname

ExplanationThe DDF error monitor has detected that a distributedagent exists at this location but not at the namedpartner location.

Whereluw-id=token

The logical unit of work ID of the thread followedby an '=' sign and a token which may be used inplace of 'luw-id' in any Db2 command that accepts'luw-id' as input.

locationThe location name of the partner site where athread with the same 'luw-id' does not exist.

lunameThe 8-character LUNAME of the partner location.

Operator responseDetermine if the inconsistency is due to networkconditions or a Db2 error. If a Db2 error is suspected,acquire documentation to diagnose the problem.

1. Console dump of Db2 address spaces (ssnmDBM1,ssnmMSTR, ssnmDIST), VTAM, and user's addressspace at the requesting site.

2. Console dump of Db2 address spaces (ssnmDBM1,ssnmMSTR, ssnmDIST), and VTAM at the serversite.

3. SYSLOG from requesting and server sites.4. LOGREC from requesting and server sites.

If an indefinite inconsistency is suspected, use theCANCEL DDF THREAD command to terminate thethread. If CANCEL DDF THREAD fails to terminate theagent, use VTAM commands to terminate the threadconversations.

Problem determinationUse the Db2 DISPLAY THREAD command with DETAILoption at each Db2 subsystem to display informationabout the agent and its conversations. Use VTAMcommands to display additional information about theconversations being used by the thread and also aboutnetwork conditions.




• SVC dump (or system dump), taken to SYS1.DUMPxxdata set, as result of an operator-initiated dumpcommand or SLIP trap exit.


.

DSNL026I LUW-ID luw-id=token APPEARS TOBE SUSPENDED PARTNERLOCATION location PARTNER LUluname

ExplanationThe DDF error monitor has detected that a distributedagent with the specified 'luw-id' at this location and atthe named partner 'location' may be suspendedindefinitely.

Whereluw-id=token

The logical unit of work ID of the thread followedby an '=' sign and a token which may be used inplace of 'luw-id' in any Db2 command that accepts'luw-id' as input.

locationThe location name of the partner site where athread with the same 'luw-id' exists.

lunameThe 8-character LUNAME of the partner location.

Operator responseDetermine if the inconsistency is due to networkconditions or a Db2 error. If a Db2 error is suspected,acquire documentation to diagnose the problem.

1. Console dump of Db2 address spaces (ssnmDBM1,ssnmMSTR, ssnmDIST), VTAM, and hung user'saddress space at the requesting site.

2. Console dump of Db2 address spaces (ssnmDBM1,ssnmMSTR, ssnmDIST), and VTAM as the serversite.

3. SYSLOG from requesting and server sites.4. LOGREC from requesting and server sites.

If an indefinite inconsistency is suspected, use theCANCEL DDF THREAD command to terminate thethread. If CANCEL DDF THREAD fails to terminate theagent, use VTAM commands to terminate the threadconversations.

Problem determinationUse the Db2 DISPLAY THREAD command with DETAILoption at each Db2 subsystem to display informationabout the agent and its conversations. Use VTAMcommands to display additional information about theconversations being used by the thread and also aboutnetwork conditions.





.

DSNL027I agent-type DISTRIBUTED AGENTWITH LUW-ID luw-id=tokenTHREAD-INFO thread-informationRECEIVED ABEND=abend-codeREASON=reason-code

ExplanationA distributed agent has abended at this location.

agent-typeInformation about the distributed agent that hasabended:REQUESTING

The thread is an allied thread that hasdistributed activity.

SERVERThe thread is a database access thread.

luw-id=tokenThe logical unit of work identifier (LUWID) and afive-digit token value. The token value can be usedin any Db2 command that accepts a LUWID asinput.




statement: dynamic or static.


• The statement identifier for the previouslyexecuted statement, if available. The statementidentifier can be used to identify the particularSQL statement. For static statements, thestatement identifier correlates to the STMT_IDcolumn in the SYSIBM.SYSPACKSTMT table. Fordynamic statements, the statement identifiercorrelates to the STMT_ID column in theDSN_STATEMENT_CACHE_TABLE table. Thatstatement might not have contributed to thecurrent failure.





abend-codeThe abend code. A value of zeros indicates that theabend code could not be determined.

reason-codeA numeric value that indicates the reason for thefailure. A value of zeros indicates that the reasoncode could not be determined.

This message might be followed by instances ofmessage DSNL028I, each of which describes a remotelocation where the distributed agent also exists andwhere diagnostic information might also need to becollected.

Problem determinationUse the information provided for the abend-code valueto determine what diagnostic information to gather.

Look for instances of message DSNL028I that identifyother locations that are involved in the abend.

Related conceptsDb2 reason codes (Db2 Codes)Related informationDSNL028Iluw-id=token ACCESSING DATA prepositionLOCATION location nettype netvalue

DSNL028I luw-id=token ACCESSING DATApreposition LOCATION locationnettype netvalue

ExplanationThis message follows DSNL027I and identifies aremote location where work might have beenoccurring for the distributed thread. This message isinformational and with the DSNL027I messageidentifies a remote location where diagnosticinformation might have to be collected.luw-id=token

The logical unit-of-work ID of the thread followedby an '=' sign and a token which may be used inplace of 'luw-id' in any Db2 command that accepts'luw-id' as input.

preposition'FOR' if the thread is a database access thread and'AT' if the thread is an allied thread that hasdistributed activity.

locationThis field contains one of the following:

• The requester's relational database name(location name)

• The requester's VTAM LU name (<luname>)• The requester's IP address

nettypeIdentifies the type of network used to access theremote site. There are two possible values:LU --

indicates that VTAM is used to connect to theremote site.

IPADDR --indicates that TCP/IP is used to connect to theremote site.

netvalueThe network address of the remote location.netvalue can be blank.

• If nettype is LU, netvalue specifies the VTAM LUname of the remote location.

• If nettype is IPADDR, netvalue specifies the IPaddress of the partner.

Problem determinationSee message DSNL027I.

DSNL029I DDF IS NOT INITIALIZED



ExplanationA -START DDF or -STOP DDF command was issuedbefore DDF was initialized during Db2 startupprocessing.

Operator responseWait for the DSN9022I 'START DB2' NORMALCOMPLETION message and re-issue the command.

DSNL030I csect-name DDF PROCESSINGFAILURE FOR LUWID=luw-idREASON=reason-code THREAD-INFO=thread-information

ExplanationA requesting conversation was terminated because ofDDF processing failure.


luw-idThe logical unit of work ID of the requesting agent,if that information is available, or a description ofthe logical unit that made the request in the format"netid.luname.000000000000".

reason-codeA numeric value that describes the nature of theDDF processing failure.




statement: dynamic or static.• The statement identifier for the previously

executed statement, if available. The statementidentifier can be used to identify the particularSQL statement. For static statements, thestatement identifier correlates to the STMT_IDcolumn in the SYSIBM.SYSPACKSTMT table. Fordynamic statements, the statement identifiercorrelates to the STMT_ID column in theDSN_STATEMENT_CACHE_TABLE table. Thatstatement might not have contributed to thecurrent failure.





System actionProcessing continues, but the system will eventuallyabend the database access agent.

Operator responseNotify the system programmer for analysis.






DSNL031I csect-name DRDA EXCEPTIONCONDITION IN RESPONSE FROMSERVER LOCATION=location-indicator FOR THREAD WITHLUWID=luwid REASON=reason-code ERROR ID=error-idCORRELATION ID=correlation-idCONNECTION ID=connection-idIFCID=ifcid SEE TRACE RECORDWITH IFCID SEQUENCENUMBER=seq-no




ExplanationA DRDA exception condition was detected in responsedata returned from the application server (AS).Possible error conditions include:

• An error reply message and severity code receivedfrom the server.

• A parsing error detected while processing a replymessage or reply data object

• A DRDA protocol violation, (for example, an objectreturned that is not valid for this command).


luw-idThe logical unit of work (LUW) ID that identifies thethread. This values is also included in the tracerecord.

location-indicatorAn indicator of the location:

• The server's relational database name• The server's VTAM LU name• The server's IP address

reason-codeThe Db2 reason code for this specific error.

error idThe module name concatenated with a 4-bytesource id that uniquely determines the sourcewithin the module where the exception isencountered.

correlation-idThe correlation identifier of the thread thatdetected the DRDA exception condition.Correlation IDs beginning with 001 through 028,inclusive, identify system agents.

connection-idThe connection name of the thread that detectedthe DRDA exception condition.

ifcid-numberThe IFCID number of the trace record that waswritten.

sequence-numberThe IFCID sequence number associated with thetrace record. The trace record contains informationthat can be used to determine what caused theDRDA exception condition, and is written to thedestination for IFCID 191. The message and thetrace record are written only the first time an erroris detected. This avoids flooding the console andthe trace. The sequence number is printed inhexadecimal.

If the sequence number is zero, then the trace datawas not externalized.

System actionAn alert was generated. Additionally, if the sequence-number is not zero, the system wrote a trace recordwith IFCID=ifcid-number to the destination for IFCID191 that can be used to diagnose the problem.

Problem determinationDetermine the destination of the trace record andlocate and print the trace record with SEQUENCENUMBER=sequence-number. The description of thereason code can be used in conjunction with OpenGroup Technical Standard, DRDA Version 3 Vol. 1:Distributed Relational Database Architecture todetermine the type of DRDA exception that has beendetected.

Related conceptsDb2 reason codes (Db2 Codes)

DSNL032I csect-name DRDA EXCEPTIONCONDITION IN REQUEST FROMREQUESTER LOCATION=location-indicator FOR THREAD WITHLUWID=luw-id REASON=reason-code ERROR ID=error-idIFCID=ifcid-number SEE TRACERECORD WITH IFCID SEQUENCENUMBER=sequence-number

ExplanationA DRDA exception condition was detected whileprocessing a command or command data receivedfrom the application requester (AR). Possible errorconditions include errors detected while processing acommand or a command data object.


location-indicatorAn indicator of the location:

• The requester's relational database name• The requester's VTAM LU name• The requester's IP address

luw-idThe logical unit of work (LUW) ID that identifies thethread. This value is also included in the tracerecord, or "NETID.LUNAME.000000000000" if theerror detected involves an invalid FMH5.



reason-codeThe Db2 reason code for this specific error.

error-idThe module name concatenated with a 4-bytesource ID that uniquely determines the sourcewithin the module where the exception wasencountered.

ifcid-numberThe IFCID number of the trace record that waswritten.

sequence-numberThe IFCID sequence number associated with thetrace record. The trace record contains informationthat can be used to determine what caused theDRDA exception condition, and is written to thedestination for IFCID 191. The message and thetrace record are written only the first time an erroris detected. This avoids flooding the console andthe trace. The sequence number is printed inhexadecimal.

If the sequence number is zero, then the trace datawas not externalized.

System actionAn alert was generated. Additionally, if the sequence-number is not zero, the system wrote a trace recordwith IFCID=ifcid-number to the destination for IFCID191 that can be used to diagnose the problem.


System programmer responseDetermine the destination of the trace record andlocate and print the trace record with SEQUENCENUMBER=sequence-number. The description of thereason code can be used in conjunction with OpenGroup Technical Standard, DRDA Version 3 Vol. 1:Distributed Relational Database Architecture todetermine the type of DRDA exception that has beendetected.


DSNL033I csect-name DDF TERMINATIONSCHEDULED DUE TO DETECTIONOF ABEND abend REASON reason

ExplanationA severe error was detected during DDF processing.DDF processing can no longer continue so DDFtermination has been scheduled. 'Csect-name' is the

Db2 module that detected the condition andrequested DDF termination.

The abend and reason might also contain additionalinformation about the cause.abend

The abend code or zeros if no abend is associatedwith the termination of DDF.

If the abend was a Db2 04E abend, the Db2 reasoncode will contain additional information about theabend.

reasonThe Db2 reason code or zeros if no Db2 reasoncode is associated with the termination of DDF.

If no abend is associated with the problem, thereason code describes the cause for thetermination.



System programmer responseDetermine the cause of the failure. Correct thecondition and restart DDF using the -START DDFcommand.

Problem determinationIf an abend is associated with the failure, a dumpmight have been provided. LOGREC will also containinformation about the abend.

DSNL034E DDF CANNOT BE STARTEDBECAUSE OF BSDSINCONSISTENCIES, ORIGINALLUNAME=original-luname, BSDSLUNAME=bsds-luname, ORIGINALLOCATION=original-location, BSDSLOCATION=bsds-location

ExplanationThe LUNAME or the LOCATION name stored in thebootstrap data set (BSDS) was changed after thedistributed data facility (DDF) was last started, butDDF still has resynchronization responsibility with oneor more partner logical units using the old LUNAMEand LOCATION name. Both the original and currentBSDS values of LUNAME and LOCATION name aredisplayed.



original-lunameThe LUNAME required for resynchronization.

bsds-lunameThe LUNAME currently stored in the BSDS.

original-locationThe LOCATION name required forresynchronization.

bsds-locationThe LOCATION name currently stored in the BSDS.

System actionDDF cannot be started until the inconsistencies arecorrected.

Operator responseInform the database administrator.

Database administrator responseTake the appropriate action, depending on whetherthere is a requirement to change the LUNAME orLOCATION name in the BSDS:

Name changed in errorUse the change log inventory (DSNJU003) utility tochange the LUNAME, LOCATION name , or bothback to the correct value. Then issue the STARTDDF command.

Name change requiredRemove all of the resynchronization responsibilitythat Db2 had using the old names. You can purgethis information, allow automaticresynchronization to take place, or use acombination of both.

You can purge resynchronization information byusing the RESET INDOUBT command with theFORCE option. You can purge all informationregardless of partner name (LOCATION (*)), or youcan selectively purge by specifying a locationname. DDF does not have to be started to use thiscommand. You can use the DISPLAY THREADcommand to generate a report of indoubt threads.This report indicates all resynchronizationresponsibility known by Db2.

If you do not purge the resynchronizationinformation, or choose to selectively purge, andyou want automatic resynchronization to occurbefore changing the names, you must first use thechange log inventory (DSNJU003) utility to changethe LUNAME, the LOCATION name, or both back tothe correct value. Then issue the START DDF. Atthis point, automatic resynchronization begins. Youcan monitor the progress by periodically using theDISPLAY THREAD command for TYPE (INDOUBT)

threads. Resynchronization does not completeuntil all needed communications paths areavailable and all needed partner logical units areavailable. If you cannot wait for availability, use theRESET INDOUBT command with the FORCE optionto purge information associated with unavailablepartners.

Related reference-DISPLAY THREAD (Db2) (Db2 Commands)-RESET INDOUBT (Db2) (Db2 Commands)-START DDF (Db2) (Db2 Commands)DSNJU003 (change log inventory) (Db2 Utilities)

DSNL035I DDF CANNOT BE STOPPEDBECAUSE AN INDOUBT DATABASE ACCESS THREAD EXISTS

ExplanationDDF is the connection manager for a database accessthread (DBAT) that is indoubt. A STOP DDFMODE(QUIESCE) command is rejected until theindoubt logical unit of work is resolved.

System actionDDF is not stopped.

Operator responseInform the database administrator.

Database Administrator Action: You have thefollowing options:

• Wait for automatic resynchronization to beperformed. When this occurs, either messageDSNL407I or DSNL415I is displayed.

After the indoubt thread is resolved, reissue theSTOP DDF command.

• Use the DISPLAY THREAD TYPE(INDOUBT)command to find the LOCATION that has coordinatorresponsibility for the indoubt LUW. Contact thatlocation and determine whether the LUW committedor aborted. Then use the RECOVER INDOUBTcommand to cause the indoubt DBAT to be resolvedwith the same decision.

After the indoubt thread is resolved, reissue theSTOP DDF command.

• Issue the STOP DDF MODE(FORCE) command. Theindoubt thread remains indoubt and can be resolvedby using automatic resynchronization after DDF isstarted again, or it can be resolved manually asdescribed above.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displaythread.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_resetindoubt.html



DSNL036I DDF THREAD logical-unit-of-work-id SPECIFIED IS INDOUBT

ExplanationA database access thread that is indoubt cannot becanceled by using the -CANCEL DDF THREADcommand.


Operator responseUse the -DISPLAY THREAD TYPE(*) command todisplay all distributed activity.

DSNL037I csect-name RESET GENERICLU luSUCCESSFUL

ExplanationThe RESET GENERICLU command successfully purgedthe VTAM sysplex information from shared memory.lu

The value supplied on the RESET GENERICLUcommand

System actionThe VTAM information contained in the sysplex sharedmemory for the indicated LU is purged.

DSNL038E csect-name RESET GENERICLU luFAILED DUE TO VTAM RTNCD=xxand FDB2=yy

ExplanationThe VTAM CHANGE,OPTCD=(SYN,ENDAFFIN) macroreturned an unexpected return code, which isdescribed by the indicated VTAM RTNCD and FDB2values.lu


xxThe hexadecimal value of the VTAM RTNCD field

yyThe hexadecimal value of the VTAM FDB2 field

System actionVTAM was not able to purge the sysplex sharedmemory information for the indicated LU.

System programmer responseRefer to z/OS Communications Server SNAProgramming for the meaning of the VTAM RTNCD andFDB2 values.

DSNL039E csect-name RESET GENERICLU luFAILED DUE TO ACTIVE VTAMSESSIONS

ExplanationThe RESET GENERICLU command was not acceptedbecause one or more active VTAM sessions exist to theindicated LU. All VTAM sessions must be terminatedbefore the command is accepted.lu


System actionThe command is rejected.

System programmer responseTerminate the VTAM sessions to the remote LU andreissue the -RESET GENERICLU command.

DSNL040E csect-name RESET GENERICLU luFAILED DUE TO INDOUBTRESOLUTION INFORMATION

ExplanationThe RESET GENERICLU command was not acceptedbecause information is currently being retained forresolution of indoubt threads for the indicated partnerLU. The DISPLAY THREAD TYPE(INDOUBT) commandcan be used to view this information.lu


System actionThe command is rejected.

System programmer responseMake sure that all indoubt threads at the remote siteare resolved before issuing the RESET GENERICLUcommand.

When Db2 performs automatic indoubt threadresolution, the information contained in the DISPLAYTHREAD TYPE(INDOUBT) display is purged at the endof the resynchronization process.


If required, use the -RESET INDOUBT command tomanually purge the indoubt resolution information.

DSNL041E csect-name DB2 GENERIC LUNAME REQUESTED, BUTREQUIRED VTAM LEVEL IS NOTINSTALLED

ExplanationThe DB2 GENERIC LUNAME installation option wasspecified. This option requires VTAM Version 4 Release2 or a later release.

System actionThe DB2 GENERIC LUNAME installation option isignored.

System programmer responseIf the DB2 GENERIC LUNAME is required, install VTAMVersion 4 Release 2 or a later release.

DSNL042E csect-name DB2 SYSPLEX TP WASINVOKED BY LU lu, BUT REQUIREDMVS LEVEL IS NOT INSTALLED

ExplanationA request for the Db2 sysplex transaction program(TP) was received by a Db2 server that is a member ofa data sharing group. The Db2 sysplex TP is used bythe requesting systems to determine which Db2systems within the group are currently available forDDF conversations.

The Db2 sysplex TP uses Workload Manager (WLM)functions in MVS Version 5 Release 2 or a later releaseto balance distributed workload among the Db2systems in the group. Because the required MVSrelease is not installed or Db2 is not registered withWLM, the Db2 sysplex TP is not able to provide therequested information.lu

The name of the LU in the network that invoked theDb2 sysplex TP

System actionThe Db2 sysplex TP returns the NETID.LUNAME of thelocal Db2 system as the only available Db2 server inthe group. The requester is not provided the names ofother Db2 systems in the group, so all sessions fromthe requester are routed to the local Db2 server.

System programmer responseInstall MVS Version 5 Release 2 or a later release ifyou want to have the Db2 sysplex TP return multipleNETID.LUNAME values to the requester or refer to theDSNL044I on why Db2 could not register with WLM.

DSNL043I csect-name RESET GENERICLU'luname' INVALID

ExplanationThe luname value specified is invalid.


lunameThe logical unit name.

The correct format for the logical unit name is eitherluname or network-id.luname, using the followingvalues:

network-idAn optional 1- to 8-character network ID.

lunameA 1- to 8-character logical unit name.

System actionThe parameter is ignored. Processing continues withthe next logical unit name, if any.

User responseDetermine the correct value for luname and reissuethe command.

DSNL044I csect-name MVS macro-nameMACRO FAILED WITHRETCODE='return-code'X ANDRSNCODE='reason-code'X

ExplanationAn MVS Workload Manager (WLM) macro returned anunexpected return code, which is described by theindicated RETCODE and RSNCODE values. DDF usesMVS Workload Manager macros to obtain data sharingsysplex routing information for incoming DDF workrequests, and to establish an MVS enclave for theexecution environment of the distributed thread.


macro-nameThe name of the MVS macro that returned theunexpected return code. The possible values are:


• IWMSRSRG: Register with WLM for sysplexrouting.

• IWMSRSRS: Request sysplex routinginformation.

• IWMSRDRS: Deregister with WLM for sysplexrouting.

• IWMECREA: Create enclave.• IWMEQRP: Query enclave

The WLM sysplex routing service macros will beappended with the contents of the LOCATIONparameter passed to it. The contents of theLOCATION parameter will either be the member'slocation name or one of the alias-names beingdefined to subset the data sharing group. If themember's location name is displayed, then thismember will not participate in WLM workloadbalancing. If a subsetting alias-name is displayed,then subsetting of the data sharing group by thatalias-name will be disabled. However, a connectionto this member of the data sharing group will beaccepted when using the alias-name instead of themember's location name.

return-codeThe hexadecimal value of the MVS return code.

reason-codeThe hexadecimal value of the MVS reason code.

System actionIf a sysplex routing macro failed, then sysplex routingmay not be performed in which case, all SQLstatements received from the client will be processedby this Db2 subsystem. If an enclave macro failed, thedistributed thread may not be able to execute in anMVS enclave, however the distributed thread willcontinue to execute as an MVS SRB.

System programmer responseUse the MVS return and reason codes to determine theproblem.

Related referenceSetting up a Service Definition (MVSProgramming: Workload Management Services)

DSNL045I csect-name ICSF function-nameFUNCTION FAILED WITHRETCODE='return-code'X ANDRSNCODE='reason-code'X

ExplanationDb2 for z/OS made an Integrated CryptographicService Facility (ICSF) call because a connection to a

remote server or a connection from a remoterequester is using encryption, but the ICSF callreturned an unexpected return code.

Db2 for z/OS uses ICSF to perform the followingfunctions:

• Creating connection keys• Generating a shared private key• Encrypting data• Decrypting data


function-nameThe name of the ICSF call that returned theunexpected return code. The possible values are:

• CSNERNG: Random Number Generate• CSNECKM: Multiple Clear Key Import• CSNFPKB: Key Token Build• CSNFPKE: Key Encrypt• CSNEENC: Encipher data.• CSNEDEC: Decipher data• CSNESYE: Symmetric Encipher• CSNESYD: Symmetric Decipher• CSNEOWH: MD5 Hash

return-codeThe hexadecimal value of the ICSF return code.

reason-codeThe hexadecimal value of the ICSF reason code.

System actionThe encryption function cannot be processed. Db2issues this message one time and does not retry theICSF services call until Db2 or DDF is restarted.

System programmer responseIf the encryption facility is not installed, take one ofthe following actions:

• Install the encryption facility before requestingencryption.

• Update the driver settings of the remote clients tonot request encryption for connections to the Db2for z/OS server.

If the encryption facility is installed, verify that it isworking correctly. Look up the return code and reasoncode in the ICSF documentation for help in finding andfixing the problem.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaw100/setsd.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaw100/setsd.htm

Related referencez/OS Cryptographic Services IntegratedCryptographic Service Facility SystemProgrammer's Guide

DSNL046I csect-name ICSF is not enabled

ExplanationThis message indicates that a cryptographic service isrequired, but the Integrated Cryptographic ServiceFacility (ICSF) is unavailable.

System actionDb2 cannot continue with the encryption or decryptionfunction.

System programmer responseIf the encryption facility is not installed, take one ofthe following actions:

• Install the encryption facility before requestingencryption.

• Update the driver settings of the remote clients tonot request encryption for connections to the Db2for z/OS server.

If the ICSF is installed, check for a related DSNL045Imessage, and verify that the ICSF service is availableand working correctly.

Related referencez/OS Cryptographic Services IntegratedCryptographic Service Facility SystemProgrammer's GuideRelated informationDSNL045Icsect-name ICSF function-name FUNCTIONFAILED WITH RETCODE='return-code'X ANDRSNCODE='reason-code'X

DSNL047I THE REQUESTED TRUSTEDCONNECTION CANNOT BEESTABLISHED TO THE LOCATIONlocation-name

ExplanationThe trusted connection that you requested cannot beestablished to the location location-name.

System actionThe attempt to create a trusted connection wasunsuccessful. A normal connection was createdwithout any attributes of a trusted context.

Problem determinationlocation-name identifies the name of the server thatcould not support the trusted connection.

DSNL048I csect-name SAF USER MAPPINGFUNCTION function-name FAILEDWITH RETURN VALUE=return-value RETURN CODE=return_codeREASON CODE=reason_codeERRORMESSAGE:saf_error_message

ExplanationThe SAF user mapping plug-in function failed. WhenDb2 receives a user registry name from a remote clientapplication, Db2 calls the SAF user mapping plug-inservice to retrieve the z/OS user ID which will be usedas the primary authorization ID for the remoteconnection.function-name

The name of the SAF user mapping function thatfailed. Possible functions can be safMappingInit(),safMappingLookup(), or safMappingTerm().

return-valueSAF user mapping function return value.

return_codeSAF user mapping function return code.

reason_codeSAF user mapping function reason code.

saf_error_messageSAF user mapping function error message detailingthe error condition.

System programmer responseRefer to the z/OS Security Server - RACF Messages andCodes for the meaning of SAF user mapping functionreturn_value, return_code. reason_code, andsaf_error_message.

DSNL065I csect-name CURRENT DDF STATEDOES NOT PERMIT STOP DDFMODE(SUSPEND)

ExplanationThe current DDF state does not allow suspendprocessing to be initiated. DDF must be started fornormal processing in order for suspend processing tobe initiated.

System actionThe command is not executed.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.csfb200/toc.htm






DSNL066I csect-name STOP DDFMODE(SUSPEND) COMPLETE

ExplanationDDF suspend processing has completed successfully.DDF has suspended all inbound activity.


DSNL067I csect-name CURRENT DDF STATEDOES NOT PERMIT START DDF

ExplanationThe current DDF state does not allow START DDFprocessing to be initiated.


DSNL068I csect-name START DDF (RESUMEPROCESSING) COMPLETE

ExplanationDDF has resumed normal processing.


DSNL069I csect-name DDF IS SUSPENDING

ExplanationDDF has initiated suspend processing.


DSNL070I csect-name DDF IS RESUMING

ExplanationDDF has initiated resume processing.


DSNL071I csect-name WAIT OR CANCELREQUIRES KEYWORD SUSPEND

ExplanationThe WAIT(n) or CANCEL(n) keywords require thatMODE(SUSPEND) be specified.


User responseAdd the missing keyword and reissue the command.

Related reference-STOP DDF (Db2) (Db2 Commands)

DSNL072I csect-name WAIT TIME EXPIRED,DDF RESUME PROCESSINGINITIATED

ExplanationThe DDF suspend process has not completedsuccessfully in the period of time specified for theWAIT keyword, so DDF resume processing has beeninitiated.

System actionDDF resume processing has been initiated.


DSNL073I csect-name CANCEL TIMEEXPIRED, CANCEL ACTIVE DBATPROCESSING HAS BEENINITIATED

ExplanationThe DDF suspend process has not completedsuccessfully in the period of time specified for theCANCEL keyword so DDF is canceling all activedatabase access threads (DBATS).

System actionDDF is attempting to terminate all active databaseaccess threads.


DSNL074I NUMBER OF CLIENTCONNECTIONS HAS EXCEEDEDexceeded-percent % OF THEMAXIMUM ALLOWED


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_stopddf.html



ExplanationThe number of increasing client connections hasexceeded either 80% or 90% relative of the value ofthe CONDBAT subsystem parameter.

percent-exceededThe percentage of the threshold specified by thevalue of the CONDBAT subsystem parameter thatwas exceeded.

The DSNL074I message is issued only when the Db2subsystem is a member of a data sharing group.

System actionThe health value reported to WLM is decreased to 50%(when the value of exceeded-percent is 80) or 25%(when the value of exceeded-percent is 90) of thecalculated Db2 system health value. This action mightenable remote client systems to direct work to othermembers which have more resources to process thework.

The modified health value remains until the number ofclient connections decreases below either the 80% or90% threshold.

System programmer responseIf a subsequent DSNL075I is displayed, no action isrequired.

Otherwise, investigate why the number of connectionshas exceeded the threshold set by the CONDBATsubsystem parameter. You can use the DISPLAYLOCATION command to determine which clientlocations are sending increasing numbers ofconnections to the Db2 subsystem. If the cause of theincreasing connections in normal workload growth,then additional monitoring might be required. If theincreasing connections are the result of and exceptioncondition, additional investigation might be required toresolve the problem.

Related referenceMAX REMOTE CONNECTED field (CONDBATsubsystem parameter) (Db2 Installation andMigration)-DISPLAY LOCATION (Db2) (Db2 Commands)Related informationDSNL075INUMBER OF CLIENT CONNECTIONS NOLONGER EXCEEDS percent-exceeded% OF THEMAXIMUM ALLOWED

DSNL075I NUMBER OF CLIENTCONNECTIONS NO LONGEREXCEEDS percent-exceeded% OFTHE MAXIMUM ALLOWED

ExplanationThe number of client connections has decreased suchthat either the 80% or 90% threshold relative to theMAX CONDBAT subsystem parameter is no longerbeing exceeded.

percent-exceededThe percentage of the threshold specified by thevalue of the CONDBAT subsystem parameter thatwas exceeded.

The health value reported to WLM will also beincreased to 50% (when the value of percent-exceededis 90) or 100% (when the value of percent-exceeded is80) of the calculated Db2 system health value.

The DSNL075I message can only be issued when theDb2 subsystem is a member of a data sharing group.



Related referenceMAX REMOTE CONNECTED field (CONDBATsubsystem parameter) (Db2 Installation andMigration)Related informationDSNL074INUMBER OF CLIENT CONNECTIONS HASEXCEEDED exceeded-percent % OF THEMAXIMUM ALLOWED

DSNL080I csect-name DISPLAY DDF REPORTFOLLOWS:

ExplanationThis message displays output from the DISPLAY DDFcommand. The output includes the status andconfiguration of DDF for the local subsystem ormember. It also includes statistics for the connectionsand threads that are controlled by DDF.


The remaining output consists of one or more of thefollowing messages, in the indicated order:

• DSNL081I: DDF status• DSNL082I and DSNL083I: Location information• DSNL084I: TCP/IP port information• DSNL085I: IP address


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_condbat.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displaylocation.html




• DSNL086I: TCP/IP domain name• DSNL087I and DSNL088I: Aliases• DSNL089I: Member IP address• DSNL090I: Subsystem parameter information

(CMTSTAT, CONDBAT, and MAXDBAT)• DSNL091I: Subsystem parameter information

(MAXCONQN and MAXCONQW)• DSNL092I and DSNL093I: DBAT and connection

information• DSNL094I: Closed client connections• DSNL096I: Detailed information for a specific alias• DSNL100I, DSNL101I, DSNL102I: Server list

information• DSNL105I and DSNL106I: DDF options• DSNL099I: End of output

DSNL081I: DDF statusThe introduction to the output is followed by theoperational status of DDF:

DSNL081I STATUS=status

statusThe DDF status, which can be one of the followingvalues:STARTD

DDF is started.STARTG

DDF is starting.STOPDF

DDF was stopped abnormally, for example, bythe STOP DDF command with theMODE(FORCE) option.

STOPDQDDF was stopped normally or is not yet started.DDF can be stopped normally by using theSTOP DDF command with the MODE(QUIESCE)option.

STOPGFDDF is in the process of stopping abnormally,for example, by the STOP DDF command withthe MODE(FORCE) option.

STOPGQDDF is in the process of stopping normally, forexample, by the STOP DDF command with theMODE(QUIESCE) option

SUSPNDDDF is suspended, for example, by the STOPDDF command with the MODE(SUSPEND)option.

SUSPNGDDF is in the process of suspending, forexample, by the STOP DDF command with theMODE(SUSPEND) option.

NOINITDDF is not configured. The value of the DDFsubsystem parameter is NO.


-STOP DDF (Db2) (Db2 Commands)DDF STARTUP OPTION field (DDF subsystemparameter) (Db2 Installation and Migration)

DSNL082I and DSNL083I: LocationinformationThe DDF status information is followed by locationinformation:

DSNL082I LOCATION LUNAME GENERICLUDSNL083I location luname genericlu

locationThe location name of DDF, as recorded in thebootstrap data set (BSDS). The location name canbe specified by one of the following methods:

• The Db2 LOCATION NAME field on the DSNTIPRinstallation panel

• The LOCATION option in the DDF statement ofthe DSNJU003 (change log inventory) utility

lunameThe DDF LU name, as recorded in the BSDS. The LUname can be specified by one of the followingmethods:

• The Db2 NETWORK LUNAME field on theDSNTIPR installation panel

• The LUNAME option in the DDF statement of theDSNJU003 (change log inventory) utility

A value of -NONE indicates one of the followingsituations:

• An LU name is not configured.• The DDF record in the BSDS already has a value

for IPNAME. Therefore, DDF did not activate itsSystems Network Architecture (SNA) orAdvanced Program to Program Communication(APPC) support.

If an LU name is configured, the luname fieldcontains the fully qualified LU name, whichconsists of a network ID, a period delimiter, andthe LU name. The network ID is determined fromVTAM after DDF is started. A network ID of NONE



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_ddf.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_ddf.html

indicates that DDF is not yet started, orinitialization with VTAM failed.

genericluThe DDF generic LU name, as recorded in theBSDS. The generic LU name can be specified byone of the following methods:

• The Db2 GENERIC LUNAME field on the DSNTIPRinstallation panel

• The GENERIC option in the DDF statement of theDSNJU003 (change log inventory) utility

A value of -NONE indicates one of the followingsituations:

• A generic LU name is not configured.• The DDF record in the BSDS already has a value

for IPNAME. Therefore, DDF did not activate itsSystems Network Architecture (SNA) orAdvanced Program to Program Communication(APPC) support.

If a generic LU name is configured and enabled,the genericlu field contains the fully qualifiedgeneric LU name, which consists of a network ID, aperiod delimiter, and the generic LU name. Thenetwork ID is determined from VTAM after DDF isstarted. A network ID of NONE indicates that theDDF is not yet started, or initialization with VTAMfailed.

The location name, LU name, and generic LU name forDDF are also included in message DSNL004I whenDDF is started.


DB2 LOCATION NAME field (Db2 Installation andMigration)DB2 NETWORK LUNAME field (Db2 Installation andMigration)DB2 GENERIC LUNAME field (Db2 Installation andMigration)DSNJU003 (change log inventory) (Db2 Utilities)“DSNL004I” on page 329

DSNL084I: TCP/IP port informationThe location information is followed by informationabout the TCP/IP port that is associated with DDF:

DSNL084I TCPPORT=tcp-port SECPORT=secure-port RESPORT=resync-port IPNAME=ip-name

tcp-portThe TCP/IP port number for the SQL listener, asrecorded in the BSDS. This port number can bespecified by one of the following methods:

• The DRDA PORT field on the DSNTIP5installation panel

• The PORT option in the DDF statement of theDSNJU003 (change log inventory) utility

A value of 0 (zero) indicates that an SQL listenerport was not specified, and DDF is not configuredto use TCP/IP network protocols.

A value of -NONE indicates that Db2 does notaccept connections on this port. One possiblereason that Db2 does not accept connections isthat the MAXDBAT subsystem parameter is set to 0(zero). The current MAXDBAT value is listed in theDSNL090I message, which is included as part ofthe DISPLAY DDF output when the DETAIL optionis specified.

secure-portThe TCP/IP port number for the secure SQLlistener, as recorded in the BSDS. This port numbercan be specified by one of the following methods:

• The SECURE PORT field on the DSNTIP5installation panel

• The SECPORT option in the DDF statement of theDSNJU003 (change log inventory) utility

A value of 0 (zero) indicates both of the followingconditions:

• A secure SQL listener port was not specified.• DDF is not configured to accept secure inbound

connections by using the Secure Socket Layer(SSL) protocol through this port number.

If a secure port is not specified, remoteconnections can still use the TCP/IP port for theSQL listener (tcp-port) and use the SSL protocol onthat port. However, DDF does not validate whetherthe connection uses SSL protocol.

A value of -NONE indicates that Db2 does notaccept connections on this port. One possiblereason that Db2 does not accept connections isthat the MAXDBAT subsystem parameter is set to 0(zero). The current MAXDBAT value is listed in theDSNL090I message, which is included as part ofthe DISPLAY DDF output when the DETAIL optionis specified.

resync-portThe TCP/IP port number for the two-phase commitresynchronization (resync) listener, as recorded inthe BSDS. This port number can be specified byone of the following methods:

• The RESYNC PORT field on the DSNTIP5installation panel

• The RESPORT option in the DDF statement of theDSNJU003 (change log inventory) utility

A value of 0 (zero) indicates that aresynchronization listener port was not specified,


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_db2locationname.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_db2locationname.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_db2networkluname.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_db2networkluname.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_db2genericluname.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_db2genericluname.html


and DDF is not configured to use TCP/IP networkprotocols.

ip-nameThe IPNAME value, as recorded in the BSDS. For adescription of the IPNAME value, see theDSNJU003 syntax information.

This value is unique to this DDF.

If this Db2 subsystem is a member of a datasharing group, the IPNAME value is unique to thatdata sharing group. If all the members of a datasharing group activate only their TCP/IPcommunications support, all members of thatgroup must be defined with the same IPNAMEvalue.

This TCP/IP port information for DDF is also includedin message DSNL004I, which is displayed when DDF isstarted.


DRDA PORT field (Db2 Installation and Migration)SECURE PORT field (Db2 Installation and Migration)RESYNC PORT field (Db2 Installation and Migration)MAX REMOTE ACTIVE field (MAXDBAT subsystemparameter) (Db2 Installation and Migration)“DSNL004I” on page 329DSNJU003 (change log inventory) (Db2 Utilities)

DSNL085I: IP addressThe TCP/IP port information is followed by the IPaddress that is associated with DDF:

DSNL085I IPADDR=ip-address

ip-addressThe IP address of DDF.

If the subsystem is a member of a data-sharinggroup, the IP address is a sysplex-wide IP address.Db2 expects this sysplex-wide IP address to beconfigured as a distributed dynamic virtual IPaddress (distributed DVIPA). A distributed DVIPAdistributes connections across the group.

A value of -NONE indicates that one or more of thefollowing conditions is true:

• DDF is not configured to use TCP/IP networkprotocols. See the tcp-port value in messageDSNL084I.

• DDF is not started.• TCP/IP initialization failed.

If both IPv4 and IPv6 addresses are configured,message DSNL085I is displayed twice, once foreach protocol type.

If the subsystem is not a member of a data sharinggroup and the listener ports are defined, DDFobtains its IP address from one of the followingplaces:

• The IP address that is recorded in the BSDS• The information that is returned by a z/OS UNIX

System Services getaddrinfo call

If the subsystem is a member of a data sharinggroup and the listener ports are defined, DDFobtains the location's sysplex-wide IP addressfrom one of the following places:

• The IP address that is recorded in the BSDS• The IP address that is bound in the TCP/IP PORTdefinition statement for the DRDA SQL port

If the IP address is recorded in the BSDS, DDFaccepts connections on any address. Otherwise,DDF accepts connections on only the IP addressesthat are displayed in messages DSNL085I andDSNL089I.


Communicating with data sharing groups (Db2Data Sharing Planning and Administration)getaddrinfo (BPX1GAI, BPX4GAI) -- Get the IPaddress and information for a service name orlocation (z/OS UNIX System ServicesProgramming: Assembler Callable ServicesReference)Starting TCP/IP support (Db2 Installation andMigration)

DSNL086I: TCP/IP domain nameThe IP address is followed by the TCP/IP domain namethat is associated with DDF:

DSNL086I domain-type DOMAIN=domain-name

domain-typeThe type of domain name that is displayed, whichcan be one of the following values:SQL

The name that is used by TCP/IP to routerequests to the location. The name isassociated with the IP address that isdisplayed in message DSNL085I.

RESYNCThe name that is used by TCP/IP to routerequests to DDF. This information is displayedonly if DDF is a member of a Db2 data sharinggroup. This name is associated with the IPaddress that is displayed in messageDSNL089I.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_drdaport.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_secureport.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_resyncport.html




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_communicatedsgroups.html


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxb100/gai.htm





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_starttcpipsupp.html


domain-nameThe domain name that is associated with thedomain type. A value of -NONE indicates thatTCP/IP is not configured or that TCP/IPinitialization failed.

This domain information is also included in messagesDSNL519I and DSNL004I.


“DSNL519I” on page 398“DSNL004I” on page 329Communicating with data sharing groups (Db2 DataSharing Planning and Administration)

DSNL087I and DSNL088I: AliasesIf aliases were defined for the DDF location by usingthe MODIFY DDF command or by using the DSNJU003(change log inventory) utility, the output includes aliasinformation:

DSNL087I ALIAS PORT SECPORT STATUSDSNL088I alias port secure-port status

aliasAn alias name.

You can manage static aliases by using theDSNJU003 (change log inventory) utility. You canmanage dynamic aliases by using the MODIFY DDFcommand and specifying the ALIAS option.

portThe TCP/IP port that is associated with the alias. A0 (zero) value indicates that a port was notspecified for the alias. However, the alias can stillbe accessed by using other active DRDA SQL ports.

This value is ignored for statically defined locationaliases in non-data-sharing environments.

secure-portThe TCP/IP secure port that is associated with thealias. A 0 (zero) value indicates that a secure portwas not specified for the alias. However, the aliascan still be accessed by using other active DRDAsecure SQL ports.

This value is ignored for statically defined locationaliases in non-data-sharing environments.

statusThe operational status of the alias, which can beone the following values:STARTG

The alias is starting. The MODIFY DDFcommand was issued with the ALIAS keywordto start the alias, and the start operation is inprogress.

STARTDThe alias is started or ready to start with thealias port. Db2 might be processing existingconnections to the alias and is accepting newconnection requests to the alias by using thealias port. Otherwise, Db2 starts accepting newconnection requests to the alias by using thealias port when the following conditionsbecome true:

• DDF is started.• The MAXDBAT subsystem parameter is set to

a value greater than 0.

STOPGThe alias is stopping. The MODIFY DDFcommand with the ALIAS keyword was issuedto stop an alias, and the stop operation is inprogress.

STOPDThe alias is stopped. Db2 does not accept newconnection requests to the alias by using thealias port. However, Db2 can still acceptrequests to the alias by using the group SQLport if DDF is active and listening on it. Thisvalue applies to only those aliases that aredefined and managed dynamically by theMODIFY DDF command with the ALIASkeyword.

CANCLGThe alias is canceling. The MODIFY DDFcommand with the ALIAS keyword was issuedto cancel an alias, and the cancel operation isin progress.

CANCLDThe alias is canceled. Db2 canceled all existingdatabase access threads (DBATs) that wereprocessing connections to the alias. Db2 doesnot accept new connection requests to thealias by using the alias port. However, Db2 canstill accept requests to the alias by using thegroup SQL port if DDF is active and listening onit. This value applies to only those aliases thatare defined and managed dynamically by theMODIFY DDF command with the ALIASkeyword.

STATICThe alias is static. Db2 accepts new connectionrequests when Db2 is available to acceptTCP/IP connection requests. This optionapplies to only those aliases that were createdby the DSNJU003 utility. Such aliases cannotbe defined or managed dynamically by theMODIFY DDF command.


-MODIFY DDF (Db2) (Db2 Commands)




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_modifyddf.html

DSNJU003 (change log inventory) (Db2 Utilities)MAX REMOTE ACTIVE field (MAXDBAT subsystemparameter) (Db2 Installation and Migration)

DSNL089I: Member IP addressIf DDF is part of a data sharing group and all of thefollowing conditions are true, the member IP addressis displayed:

• DDF is configured to use TCP/IP network protocols.See the tcp-port value in message DSNL084I.

• DDF is started.• TCP/IP initialization was successful.

DSNL089I MEMBER IPADDR= ip-address

ip-addressThe IP address that is associated with the specificmember of the group or with a specific locationalias that represents a member or subset ofmembers. This value is the IP address that isreturned to a client in the server list for thepurposes of workload balancing.

If both IPv4 and IPv6 addresses are configured,message DSNL089I is displayed twice, once for eachprotocol type.

DDF obtains its member IP address from one of thefollowing places:

• The IP address that is specified on the TCP/IP PORTstatement by using the BIND keyword

• The IP address that is recorded in the BSDS• The information that is returned by a z/OS UNIX

System Services getaddrinfo call


Communicating with data sharing groups (Db2 DataSharing Planning and Administration)getaddrinfo (BPX1GAI, BPX4GAI) -- Get the IPaddress and information for a service name orlocation (z/OS UNIX System Services Programming:Assembler Callable Services Reference)Starting TCP/IP support (Db2 Installation andMigration)

DSNL090I: Subsystem parameterinformation (CMTSTAT, CONDBAT, andMAXDBAT)If the DETAIL option was specified on the DISPLAYDDF command, the output also includes subsystemparameter information that is associated with DDF:

DSNL090I DT=dt CONDBAT= condbat MDBAT= mdbat

dtThe DDF thread value. This value corresponds tothe CMTSTAT subsystem parameter. dt can haveone of the following values:A

DDF is configured with DDF THREADS ACTIVE.I

DDF is configured with DDF THREADSINACTIVE.

condbatThe maximum number of inbound connections.This value corresponds to the CONDBATsubsystem parameter.

mdbatThe maximum number of database access threads(DBATs). This value corresponds to the MAXDBATsubsystem parameter.

This value determines the maximum number ofactive slots, which means the maximum number ofconcurrent active DBATs that can potentiallyexecute SQL.


DDF THREADS field (CMTSTAT subsystemparameter) (Db2 Installation and Migration)MAX REMOTE CONNECTED field (CONDBATsubsystem parameter) (Db2 Installation andMigration)MAX REMOTE ACTIVE field (MAXDBAT subsystemparameter) (Db2 Installation and Migration)

DSNL091I: Subsystem parameterinformation (MAXCONQN and MAXCONQW)If the DETAIL option was specified on the DISPLAYDDF command, the output also includes subsystemparameter information that is associated with DDF:

DSNL091I MCONQN=maxconqn-value MCONQW=maxconqw-value

maxconqn-valueThe depth of the queue of connections that arewaiting for a DBAT to process the next request.When this value is reached, and the threshold thatis specified by the MAXDBAT subsystem parameteris also reached, Db2 closes the oldest waitingclient connection.

This value corresponds to the MAXCONQNsubsystem parameter.

maxconqw-valueThe maximum amount of time that a clientconnection waits for a thread to process itsrequest. Db2 attempts to close any connectionthat waits longer than this value.













https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_cmtstat.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_cmtstat.html






This value corresponds to the MAXCONQWsubsystem parameter.


CONN QUEUE MAX DEPTH field (MAXCONQNsubsystem parameter) (Db2 Installation andMigration)CONN QUEUE MAX WAIT field (MAXCONQWsubsystem parameter) (Db2 Installation andMigration)

MAX REMOTE ACTIVE field (MAXDBAT subsystemparameter) (Db2 Installation and Migration)

DSNL092I and DSNL093I: DBAT andconnection informationIf the DETAIL option was specified on the DISPLAYDDF command, the output also includes the followinginformation:

• The number of active, inactive, queued, anddisconnected database access threads (DBATs)

• The number of queued and inactive connections

DSNL092I ADBAT=adbat QUEDBAT=quedbat INADBAT=inadbat CONQUED=conquedDSNL093I DSCDBAT=dscdbat INACONN=inaconn IUDBAT=iudbat

adbatThe current number of DBATs. This numberincludes DBATs that are actively associated withwork for remote connections and disconnectedDBATs.

This value increases as new DBATs are created orwhen inactive DBATs become active. This valuedecreases as DBATs terminate or become inactiveor as disconnected DBATs terminate. When thisvalue reaches or exceeds the MAXDBAT value,newly attached connections or new work onexisting inactive connections or threads might bequeued. This queueing occurs if no disconnectedDBATs are available to service the work.

The MAXDBAT value is shown in messageDSNL090I.

quedbatThe cumulative number of the following new workitems that had to wait for a DBAT to becomeavailable:

• Newly attached connections• New work on inactive connections• New work on inactive DBATs• New or existing work is suspended because it

exceeded the exception threshold for the

MONITOR THREADS keyword in a monitorprofile.

This value is a cumulative counter that isincremented for one of the following reasons:

• The MAXDBAT limit is reached.• An exception threshold for the MONITOR

THREADS keyword in theDSN_PROFILE_ATTRIBUTES table wasexceeded. That exception threshold limits theconcurrent number of DBATs for certainconnections.

This value corresponds to the QDSTQDBT field inIFCID 1. The quedbat counter is reset only whenthis Db2 subsystem is restarted.

A non-zero value suggests that performance andthroughput might be affected. If so, considerincreasing the MAXDBAT value.

The MAXDBAT value is shown in messageDSNL090I.

inadbatThe current number of inactive DBATs (which werepreviously called type 1 inactive threads). Thisvalue applies only if the dt value in messageDSNL090I indicates that DDF INACTIVE support isenabled.

For more information about any DBATs that areincluded in this number, look at the output fromthe DISPLAY THREAD command with theTYPE(INACTIVE) option. The DISPLAY THREADoutput begins with message DSNV401I.

conquedThe current number of connection requests thatare queued and are waiting to be serviced. Thisvalue applies only if the dt value in messageDSNL090I indicates that DDF INACTIVE support isenabled.

These connections can be newly attachedconnections or inactive connections for which anew request arrived from the client. The number ofinactive connections is shown in messageDSNL093I.

These requests cannot be processed when one ofthe following conditions occur:

• The maximum number of DBATs is reached, andno disconnected DBATs exist to process therequest.

The maximum number of threads is reachedwhen the adbat value is equal to or greater thanMAXDBAT value. (The MAXDBAT value is shownin message DSNL090I.) When this situationoccurs, processing continues for these queued


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_maxconqn.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_maxconqw.html





connections when another active DBAT releasesits slot either by terminating or by moving to theinactive state.

• An exception threshold will be exceeded for theMONITOR THREADS keyword in theDSN_PROFILE_ATTRIBUTES table if theconnection request is processed.

• DDF is suspended or suspending. See the statusvalue in message DSNL081I. Processingcontinues when DDF is started.

dscdbatThe current number of disconnected DBATs. Thisvalue applies only if the dt value in messageDSNL090I indicates that DDF INACTIVE support isenabled.

This value indicates the number of DBAT poolthreads. DBAT pool threads are the databaseaccess threads that are available to service queuedconnections requests. The DBATs that are includedin this number are also accounted for in the adbatvalue.

Over time, disconnected DBATs can hold allocationduration locks. An allocation duration lock is a lockthat persists across commit boundaries. This typeof lock requires the connection to be deallocatedor the thread to be enabled if it is inactive. You canrelease these allocation duration locks byterminating these DBATs. You can terminatedisconnected DBATs by using one of the followingmethods:

• Issue the STOP DDF command with theMODE(SUSPEND) option. Stopping DDF withMODE(SUSPEND) terminates these disconnectedDBATs without affecting current or newconnections. However, activity on these currentor new connections is not processed until DDF isstarted.

• Change the value of the POOLINAC subsystemparameter. This parameter controls the length oftime after which unused disconnected DBATs areto be automatically terminated.

inaconnThe current number of inactive connections (whichwere previously called type 2 connections). Thisvalue applies only if the dt value in messageDSNL090I indicates that DDF INACTIVE support isenabled.

This value represents connections with clientswhere the client last ended a unit of work either bya commit or rollback operation. This operationcaused Db2 to change the state of the connectionto inactive, which means that the DBAT isseparated from the connection. The connectionbecomes inactive while the DBAT is made available

to service new client connections or to service newrequests on existing client connections.

This value is not included in the inadbat value.When a new request arrives from the client systemon the connection, the connection is then moved tothe conqued value.

For more information about any connections thatare included in this number, look at the outputfrom the DISPLAY THREAD command with theTYPE(INACTIVE) option. The DISPLAY THREADoutput begins with message DSNV401I.


POOL THREAD TIMEOUT field (POOLINACsubsystem parameter) (Db2 Installation andMigration)-DISPLAY THREAD (Db2) (Db2 Commands)-STOP DDF (Db2) (Db2 Commands)“DSNV401I” on page 979

DSNL094I: Closed client connectionsThe output also includes information aboutconnections that were closed if both of the followingconditions are true:

• The DETAIL option was specified on the DISPLAYDDF command

• The Db2 subsystem is a member of a data sharinggroup

DSNL094I WLMHEALTH=health-value CLSDCONQN=number-closed CLSDCONQW=wait-closed

health-valueThe health indicator value that was last reported toWLM for the Db2 subsystem. This value is anumber from 0 to 100.

number-closedThe number of client connections that were closedbecause the value of the MAXCONQN subsystemparameter was reached since DDF was laststarted.

wait-closedThe number of client connections that were closedbecause the value of the MAXCONQW subsystemparameter was reached since DDF was laststarted.


IWM4HLTH – Setting Server Health Indicator (MVSProgramming: Workload Management Services)CONN QUEUE MAX DEPTH field (MAXCONQNsubsystem parameter) (Db2 Installation andMigration)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_poolinac.html





http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaw200/iea3w201374.htm





CONN QUEUE MAX WAIT field (MAXCONQWsubsystem parameter) (Db2 Installation andMigration)

DSNL096I: Detailed information for aspecific aliasIf the ALIAS and DETAIL options were specified on theDISPLAY DDF command, the output also includesdetailed information about the specific location alias:

DSNL096I ADBAT=active-dbats CONQUED=concurrent-queued TCONS=total-connections

active-dbatsThe number of active DBATs that are currentlyprocessing requests on behalf of the specifiedalias.

concurrent-queuedThe number of connection requests that arecurrently queued and waiting to be serviced onbehalf of the specified alias.

total-connectionsThe total number of remote connections that arecurrently associated with the alias.

DSNL100I, DSNL101I, DSNL102I: Serverlist informationThe output also includes server list information if thefollowing conditions are true:

• The DETAIL option was specified on the DISPLAYDDF command

• DDF is part of a data sharing group• DDF is configured to use TCP/IP (If the value of tcp-

port in message DSNL084I is NONE, DDF is notconfigured to use TCP/IP.)

The following server list entry information is displayedfor each DDF location or alias that registered to WLMas part of the data sharing group:

DSNL100I LOCATION SERVER LIST: DSNL101I WT IPADDR IPADDRDSNL102I weight ipv4-address ipv6-address

Message DSNL102I is repeated for each server listentry.

The server list information is provided to remoteclients that are balancing the sysplex workload. Theserver list information might represent a singlemember of the data sharing group or a location aliasthat represents either a single member or a subset ofmembers. This information influences which DDF issent future work. DDF responds with an updated

server list when DDF generates the response to aconnection request or a connection reuse request.

weightThe WLM weight for the DDF location or locationalias that is identified by the IP addresses. If novalue is displayed, WLM indicates that DDF has nocapacity and the entry is not included in the serverlist that is provided to the remote clients.

ipv4-addressThe IPv4 address that is used to identify a DDFlocation or location alias that is registered to WLM.The address is in colon-hexadecimal format. If noIPv4 address is configured, this IP address is notdisplayed.

ipv6-addressThe IPv6 address that is used to identify a DDFlocation or location alias that is registered to WLM.The address is in colon-hexadecimal format. If noIPv6 address is configured, this IP address is notdisplayed.


Communicating with data sharing groups (Db2 DataSharing Planning and Administration)

DSNL105I and DSNL106I: DDF optionsThe output also includes a list of the DDF optionvalues:

DSNL105I CURRENT DDF OPTIONS ARE: DSNL106I option-name = option-value

One instance of message DSNL106I is displayed foreach option.

option-nameThe DDF option.

option-valueThe value of the DDF option.

DSNL099I: End of outputThe DISPLAY DDF output ends with the followingmessage:

DSNL099I csect DISPLAY DDF REPORT COMPLETE










Related reference-DISPLAY DDF (Db2) (Db2 Commands)

DSNL081I STATUS=status

ExplanationThis message is a section of output from the DISPLAYDDF command, which is part of message “DSNL080I”on page 346.

DSNL082I LOCATION LUNAME GENERICLU


DSNL083I location luname genericlu


DSNL084I TCPPORT=tcp-portSECPORT=secure-portRESPORT=resync-portIPNAME=ip-name


DSNL085I IPADDR= ip-address


DSNL086I domain-type DOMAIN=domain-name


DSNL087I ALIAS PORT SECPORT STATUS


DSNL088I alias port secure-port status


DSNL089I MEMBER IPADDR= ip-address


DSNL090I DT=dt CONDBAT=condbatMDBAT=mdbat


DSNL091I MCONQN=maxconqn-valueMCONQW=maxconqw-value


DSNL092I ADBAT=adbat QUEDBAT=quedbatINADBAT=inadbatCONQUED=conqued


DSNL093I DSCDBAT=dscdbatINACONN=inaconn



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displayddf.html

DSNL094I WLMHEALTH=health-valueCLSDCONQN=number-closedCLSDCONQW=wait-closed


DSNL096I ADBAT=active-dbatsCONQUED=concurrent-queuedTCONS=total-connections


DSNL099I csect DISPLAY DDF REPORTCOMPLETE


DSNL100I LOCATION SERVER LIST:


DSNL101I WT IPADDR IPADDR


DSNL102I weight ipv4-address ipv6-address


DSNL105I CURRENT DDF OPTIONS ARE:

ExplanationThis message introduces a list of DDF options inresponse to a DISPLAY DDF command or at DDFstartup.

The DISPLAY DDF output is described in message“DSNL080I” on page 346.

DSNL106I option-name = option-value

ExplanationThis message displays DDF options in response to aDISPLAY DDF command or at DDF startup.

The DISPLAY DDF output is described in message“DSNL080I” on page 346.

DSNL199I NO ALIAS FOUND

ExplanationThe DISPLAY DDF command was issued with theALIAS keyword, but the specified alias was not found.


User responseIssue the DISPLAY DDF command to verify that thespecified alias exists and reissue the DISPLAY DDFALIAS command with the correct alias name.

Related reference-DISPLAY DDF (Db2) (Db2 Commands)

DSNL200I DISPLAY LOCATION REPORTFOLLOWS-

ExplanationThis message displays output from the DISPLAYLOCATION command.

• Output heading• No locations found• Truncated output• Detail output• Output conclusion

Output headingThe output heading is followed by information aboutconnections with remote locations:

LOCATIONThe identifier for the remote location.

• For TCP/IP requester connections, the location isthe IP address concatenated with the portnumber of the remote location. For TCP/IP serverconnections, the location is the IP address of theremote location.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displayddf.html

• For SNA connections, the location is the LU nameof the remote location.

PRDIDAn alphanumeric string that identifies the product.

The format of product identifier values ispppvvrrm, where ppp is a 3-letter product code(such as DSN for Db2), vv is the version, rr is therelease, and m is the modification level. Forexample, DSN11015 identifies Db2 11 in new-function mode, the value is ‘DSN11015'. Theproduct code (ppp) is one of the following values:

AQT for IBM Db2 Analytics Accelerator for z/OSARI for DB2 Server for VSE & VMDSN for Db2 for z/OSHTP for non-secure HTTP URL connections forDb2 native REST servicesHTS for secure HTTPS connections for Db2native REST servicesJCC for IBM Data Server Driver for JDBC andSQLJQSQ for DB2 for iSQL for Db2 for Linux®, UNIX, and Windows

Modification (m) values have the followingmeanings:0

Conversion and enabling-new-function modesfor migration from DB2 10 (CM10, CM10*,ENFM10, and ENFM10*)

5New-function mode.

TThe connection type with the remote location.Expected values are:R

A requester connection from the localsubsystem that is accessing a remote system.

SA server connection from a remote system thatis accessing the local subsystem.

GA server connection from a remote system thatis accessing the local subsystem and hasindicated that it is a Db2 Connect server/gateway.

ATT and CONNSThe type and number of connections with thepartner location. When the ATT column is blank,the value of CONNS is the total number ofconnections with the partner location. The ATTcolumn is blank unless the DETAIL option isspecified.

The meanings of the ATT values are:

AESThe connection uses AES encryption.

CBFThe connection is a secondary connection foran application that uses package-basedcontinuous block fetch.

IPSThe connection uses Internet Protocol security(IPSec).

TLSThe connection uses a secure sockets layer(SSL) that is provided by ApplicationTransparent-Transport Layer Security (AT-TLS).

TRSThe connection is a trusted connection.

WLBThe connection is from a client that is usingSysplex workload balancing.

XAThe connection is part of a distributedtransaction.

No locations foundWhen the DISPLAY LOCATION command is unable tofind any locations that are associated with thespecified list of locations, a message line indicates thatno locations were found.

If all locations were specified, there is no distributedactivity. If a location list was specified, reissue theDISPLAY LOCATION command with the LOCATION(*)parameter to display information for all locations.

Truncated outputIf the output was generated in response to a commandfrom an MVS console and more than 254 responsemessages were generated, the output is truncated. Amessage line indicates this truncation.

You can reissue the DISPLAY LOCATION command andspecify a specific location or list of locations to seecomplete output for that context.

Detail outputWhen a DISPLAY LOCATION command is issued withthe DETAIL option, the output might contain additionallines for each remote location.

The output might contain one or more lines thatprovide information about the number of connectionsfrom or to remote systems that have certain attributes:

LOCATIONThe identifier for the remote location.


• For TCP/IP requester connections, the location isthe IP address concatenated with the portnumber of the remote location. For TCP/IP serverconnections, the location is the IP address of theremote location.

• For SNA connections, the location is the LU nameof the remote location.

PRDIDAn alphanumeric string that identifies the product.


AQT for IBM Db2 Analytics Accelerator for z/OSARI for DB2 Server for VSE & VMDSN for Db2 for z/OSHTP for non-secure HTTP URL connections forDb2 native REST servicesHTS for secure HTTPS connections for Db2native REST servicesJCC for IBM Data Server Driver for JDBC andSQLJQSQ for DB2 for iSQL for Db2 for Linux, UNIX, and Windows



5New-function mode.

TThe connection type with the remote location.Expected values are:R

A requester connection from the localsubsystem that is accessing a remote system.

SA server connection from a remote system thatis accessing the local subsystem.

GA server connection from a remote system thatis accessing the local subsystem and hasindicated that it is a Db2 Connect server/gateway.

ATT and CONNSThe number of connections that are associatedwith the remote location and that have the

attribute that is identified by the ATT column.Because more than one attribute might apply tothe same connection, the total number ofconnections is not the sum of the numbers for thedifferent attributes. The expected values for ATTare:AES

Using security credentials with AES encryption.IPS

Using IPSec.TLS

SSL using Application Transparent-TransportLayer Security (AT-TLS).

TRSUsing trusted context.

WLBUsing workload balancing connections.

XAUsing XA transaction manager processing.

The output might also include lines that containdetailed information about the connections that areassociated with the Db2 system thread. A line that isidentified by the partial message number L203provides descriptive headings. The lines that follow areidentified by the partial message number L204.

SYSTASKDescribes the Db2 system threads. The expectedvalues are:SYSPLX-x

Indicates SNA-related SYSPLEX processingwhere Db2 systems periodically createconnections to a remote data sharing group toobtain WLM balancing information that isrelated to all members of the group.

The expected values of x are:

OThe local Db2 system is contacting aremote member of a data sharing group torequest WLM balancing information.

IThe local Db2 system is receiving aconnection that requests WLM balancinginformation.

RESYNCA connection that is used to resynchronize aunit of work that encountered a previousthread or communication error. One line isdisplayed for each thread that needsresynchronization with the remote site.

SESSIDThe identifier of the session:


• For SNA network connections, the VTAM-definedsession instance identifier of the session onwhich the conversation is executing. If thesession identifier is not applicable, this fieldcontains zeros.

You can use the VTAM DISPLAY NET,ID=db2-luname,SCOPE=ACT command to obtain the fullsession ID. The DISPLAY NET command lists allsessions (SID) for the Db2 logical unit. Scan theDISPLAY NET output for the complete SID.

• For Internet Protocol network connections, astring in the format local:remote, where:local

Specifies the local Db2 system's TCP/IP portnumber.

remoteSpecifies the remote partner's TCP/IP portnumber.

AThe connection activity:N

The connection is active in the network.W

The connection is suspended in Db2 and iswaiting for VTAM or TCP/IP notification that thefunction is complete.

blankNo specific activity condition exists.

STThe status of the connection:A

The connection is in allocation.C

Session limits are being negotiated (CNOS)with the SNA partner before connectionallocation.

DThe connection is in deallocation.

RReceiving.

SSending.

blankNo specific status condition exists.

TIMEThe timestamp of the last message that is sent orreceived on the connection, in the formatyydddhhmmssth, whereyy

The last two digits of the year.

dddThe number of the day in the year. Forexample, February 1 is represented as 032.

hhmmssthThe time of day in 24-hour format, tohundredths of the second.

Output conclusionThe following line identifies the end of the output ofthe DISPLAY LOCATION command:

DISPLAY LOCATION REPORT COMPLETE



Related tasksDisplaying information about connections withother locations (Db2 Administration Guide)Related reference-DISPLAY LOCATION (Db2) (Db2 Commands)

DSNL203I L203-SYSTASK SESSID A ST TIME

ExplanationThis message forms the heading for the listing of Db2system threads that communicate with otherlocations. This message is issued when a detail displayis specified on the DISPLAY LOCATION command. Fordescriptions of the message contents, see“DSNL200I” on page 356.

The message number and subsystem recognitioncharacter are not included in this message. However,L203 is included in the message text to identify themessage.


Related reference-DISPLAY LOCATION (Db2) (Db2 Commands)Related informationDSNL200IDISPLAY LOCATION REPORT FOLLOWS-

DSNL204I L204-system-task session-IDactivity status time


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_displayconnectioninfo.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_displayconnectioninfo.html



ExplanationThis message follows the DSNL203I message for aremote location when a detail display is specified onthe DISPLAY LOCATION command. This message isdisplayed for each conversation owned by a Db2system thread that communicates with the site. Fordescriptions of the message contents, see“DSNL200I” on page 356.

The message number and subsystem recognitioncharacter are not included in this message. However,L204 is included in the message text to identify themessage.


Related reference-DISPLAY LOCATION (Db2) (Db2 Commands)Related informationDSNL200IDISPLAY LOCATION REPORT FOLLOWS-

DSNL206I csect-name named-commandCOMMAND INVALID, reason

ExplanationThe specified command could not be processed.


named-commandThe command that could not be processed.

reasonThe reason that the command could not beprocessed.


DSNL300I csect-name MODIFY DDF REPORTFOLLOWS:

ExplanationProcessing of the MODIFY DDF command has begun.Additional messages about the command follow thismessage. Message DSNL301I is issued whencommand processing is complete.




Related reference-MODIFY DDF (Db2) (Db2 Commands)

DSNL301I csect-name MODIFY DDF REPORTCOMPLETE

ExplanationProcessing of the MODIFY DDF command is complete.





DSNL302I option-name IS SET TO option-value

ExplanationA MODIFY DDF command has changed an option.

option-nameThe name of the DDF processing option.

option-valueThe new value of the named processing option.When option-name is PKGREL, possible values are:BNDOPT

When a connection which has used a highperformance DBAT terminates, the highperformance DBAT is also be deallocated.

BNDPOOLDDF processing is the as BNDOPT, with thefollowing exception. When a connection thatwas used for a high performance DBATterminates, the high performance DBAT ispooled. The pooled DBAT can then be used byanother connection that presents a request tothe subsystem.





COMMITPackages are always allocated underRELEASE(COMMIT) rules regardless of theirpackage RELEASE bind option value.

When an access thread has completed a unit ofwork, and the DBAT can be pooled, DDF poolsthe DBAT, makes an accounting record, deletesthe current WLM enclave, and inactivates theconnection. Pooled access threads release allpackage allocation locks.

If the CMTSTAT subsystem parameter is set toACTIVE, then the message will always indicatethat PKGREL IS SET TO COMMIT, regardless ofthe value specified on the command.




DSNL303I THE MODIFY DDF COMMANDFAILED WITH RC=return-code andRSN=reason-code

ExplanationA BSDS error was encountered.

return-codeDb2 return code from the BSDS function.

reason-codeDb2 reason code from the BSDS function.

System actionThe command is not processed.

User responseAnalyze the return code and reason code to determinewhat type of error occurred. Refer to messagesDSNJ107I and DSNJ108I for more information.

DSNL304I THE ALIAS alias-name ALREADYEXISTS.

ExplanationThe MODIFY DDF command was issued to add anALIAS but the requested alias name already exists andthe alias cannot be added.

alias-nameThe name of the location alias.


User responseSpecify an alias that does not already exist. You canuse the output from DISPLAY DDF command to see thelist of aliases that are currently defined.

DSNL305I THE ALIAS alias-name DOES NOTEXIST.

ExplanationThe MODIFY DDF command was issued against analias that does not exist.alias-name

The name defines the location alias.


User responseSpecify an alias that already exists. You can use theoutput from the DISPLAY DDF command to see the listof aliases that are currently defined.

DSNL306I THE MAXIMUM NUMBER OFSUPPORTED ALIASES HAS BEENEXCEEDED.

ExplanationThe modify DDF command was issued to add a newalias, but the new alias would exceed the maximumnumber of aliases that can be defined. You can defineas many as 40 aliases by using the MODIFY DDFcommand.


User responseDelete unneeded aliases before adding additionalaliases. You can use the output from the DISPLAY DDFcommand to see the list of currently defined aliases.

DSNL307I invalid-value IS NOT A VALIDPARAMETER FOR keyword.



ExplanationAn invalid parameter value is specified for the MODIFYDDF command.invalid-value

The invalid value that was specified.keyword

The option keyword for which the invalid value wasspecified.IPv4

invalid-value is not in the dotted decimalformat.

IPv6invalid-value is not in the colon hexadecimalformat.

PORTinvalid-value is not a decimal number between1 and 65535, including 65535.

SECPORTinvalid-value is not a decimal number between1 and 65535, including 65535.

ALIASinvalid-value is not a valid alias name. The aliasname must meet all of the followingrequirements:

• Contains a maximum of 16 characters• Contains only letters (excluding alphabetic

extenders), numbers, or the underscorecharacter.

• Begins with a letter.


User responseReissue the command and specify a value in the validformat for the keyword that you specified.

DSNL308I NO address-port IS DEFINED FORTHE ALIAS alias-name.

ExplanationThe MODIFY DDF command was issued to delete an IPaddress or port , but an IP address or port is notassociated with the ALIAS.address-port

One of the following values:IPV4 ADDRESS

No IPv4 address is defined for the alias.IPV6 ADDRESS

No IPv6 address is defined for the alias.

PORTNo port is defined for the alias.

SECPORTNo secure port is defined for the alias.



User responseUse the output from the DISPLAY DDF command withthe ALIAS keyword to see the list of IP addresses,ports, and secure ports that are associated with eachalias.

DSNL309I MEMBER-SPECIFIC IPADDRESSES ARE NOT DEFINED.

ExplanationDDF is stopped and its TCP/IP configuration isunknown or DDF is started but configured to receiveonly from a specific IP address.

To issue a MODIFY DDF command with the ALIASkeyword and the IPV4 or IPV6 option, DDF must beconfigured to receive from any IP address. Toconfigure DDF to receive from any IP address, the DDFcommunications record that is defined in the BSDSmust be configured with the DDF IPV4 or IPV6 option.The MODIFY DDF command can be used to add ormodify alias IP addresses only when an IP address isdefined by the DSNJU003 utility and not by the PORTstatement of the TCP/IP profile.


User responseUse the output from DSNJU004 utility (the DDFcommunication record) to verify that no IP addresswas specified in the BSDS. Specify at least one IPaddress by using the DSNJU003 utility.

DSNL310I THE ALIAS keyword keyword-valueIS ALREADY IN USE.

ExplanationThe port number specified for the PORT or SECPORTkeyword in the MODIFY DDF command is already inuse for the location, or for a different alias.


keywordPORT or SECPORT

keyword-valueThe value specified for the PORT or SECPORTkeyword.


User responseUse the output from the DISPLAY DDF command tosee the ports that are defined for each alias andlocation name.

DSNL311I THE ALIAS alias-name CANNOT BESTARTED.

ExplanationThe specified alias cannot be started because it is notstopped or canceled.



User responseUse the output from DISPLAY DDF command to checkthe status of each alias. Only stopped or canceledaliases can be started.

DSNL312I THE ALIAS alias-name CANNOT BESTOPPED OR CANCELED.

ExplanationThe MODIFY DDF command was issued with the ALIASparameter to stop or cancel an alias but the alias is notstarted.alias-name

The name of the location alias.


User responseUse the output from DISPLAY DDF command to checkthe status of each alias. Only started aliases can bestopped, and only started aliases can be canceled.

DSNL313I THE ALIAS alias-name CANNOT BEMODIFIED OR DELETED.

ExplanationThe MODIFY DDF command was issued to modify anattribute of an alias that is already started. The aliasmust be stopped or canceled before it can be modifiedor deleted.

alias-nameThe name that specifies the location alias.


User responseStop or cancel the specified alias, and then modify thealias attribute, or delete the alias. Use the output fromDISPLAY DDF command (DSNL088I) to see the statusof each alias.

DSNL314I THE ALIAS alias-name IS state.

ExplanationThe MODIFY DDF command was issued with the ALIASkeyword to start, stop, or cancel an alias, and thespecified operation was successful.alias-name

The name of the location alias.state

Whether the alias was STARTED, STOPPED, orCANCELED.

System actionThe system action depends on the action that wassuccessful:STARTED

Db2 begins accepting new connections for thealias.

STOPPEDDb2 stops accepting new connections to the alias.All database access threads processingconnections to the specified alias have finishedtheir processing.

CANCELEDDb2 stops accepting new connections to the aliasand cancels all existing connections.



DSNL315I A DYNAMICALLY DEFINED ALIASWITH NAME alias-name ALREADYEXISTS.

ExplanationAn alias that was defined by the DSNJU003 utility hasthe same name as an existing alias that was alreadydefined by the MODIFY DDF commands. The new aliasthat was defined by the DSNJU003 utility is ignoredbecause the alias that was defined by the MODIFYDDF command takes precedence.

System actionThe existing alias that was defined by the MODIFY DDFcommand is used and new the statically defined aliasis ignored.

User responseYou can define location aliases statically by using theusing DSNJU003 utility or dynamically by using theMODIFY DDF command. Dynamic aliases arepreferable because you can define and modify themwithout stopping and restarting Db2 or DDF. When astatic and dynamic alias each have the same name,only the dynamic alias is used. If you want to use thestatically defined alias instead, use the MODIFY DDFcommand to delete the dynamic location alias that hasthe matching name. You can use the output fromDISPLAY DDF command to see the list of aliases thatare currently defined. The alias status is 'STATIC' forstatically defined aliases.

DSNL400E INDOUBT THREAD RESOLUTIONWITH COORDINATOR locationSHOWS HEURISTIC DAMAGE FORluwid=token - REMOTE COMMITVERSUS LOCAL ABORT.INFORMATION RECORDED INTRACE RECORD WITH IFCID=207AND IFCID SEQUENCENUMBER=seq-no1 AND IN TRACERECORD WITH IFCID=203 ANDIFCID SEQUENCE NUMBER=seq-no2

ExplanationDb2 has participant responsibility in the logical unit ofwork identified by 'luwid=token'. Resolution with thecoordinator identified by 'location' shows heuristicdamage occurred. The Db2 thread representing thelogical unit of work was previously resolved using theRECOVER INDOUBT command. The action taken wasto abort the thread. Subsequently, communication was

reestablished with the coordinator and resolutionshows that the coordinator committed the thread.

• The application was told that commit succeeded.• Any resources updated at the coordinator were

committed.• Updated resources at this Db2 were rolled back.

locationThe field contains one of the following:



luwid=tokenThe global logical unit of work id and the localtoken that identify the thread.

seq-no1The IFCID sequence number associated with the207 trace record. The sequence number is printedin hexadecimal format. If the sequence number iszero, IFCID 207 was not active or it was active witha destination of the resident trace table only. IFCID207 is a member of statistics class 4, which has adefault destination of SMF. This trace record iswritten when the heuristic damage condition wasdetected and contains information about thedamage condition.

seq-no2The IFCID sequence number associated with the203 trace record. The sequence number is printedin hexadecimal format. If the sequence number iszero, IFCID 203 was not active or it was active witha destination of the resident trace table only. IFCID203 is a member of statistics class 4, which has adefault destination of SMF. This trace record waswritten when the heuristic decision to commit orabort was made and contains information aboutthe decision, including the names of anydownstream participants.

System actionAlert A004 is generated. A trace record whoseIFCID=207 is written. Indoubt resolution with thecoordinator completes.

System programmer responseDetermine the destination of statistics class 4 andlocate and print the trace record with SEQUENCENUMBER='seq-no1'. Call the database administrator.

Database Administrator Action: Correct the damage.This is not an easy task. Since the time of the heuristicaction, the data that was aborted with the RECOVER


INDOUBT command might have been used by manyapplications - read and/or write. Correcting thedamage might involve reversing the effects of theseapplications as well. Tools available are:

• The statistics trace class 4 contains an IFCID 207trace record. This record contains the RBA of the firstDb2 log record written for the logical unit of workwhose LUWID is included in this message.

• The DSN1LOGP utility provides a summary reportthat identifies the table spaces modified by thelogical unit of work and any downstream participantlocations involved in the logical unit of work.

• DISPLAY THREAD TYPE(INDOUBT) displays the RBAof the first Db2 log record written for the logical unitof work whose LUWID is included in this message.This information continues to appear in the DISPLAYTHREAD report until it is purged with the RESETINDOUBT command.

Contact your IBM Support Center for furtherassistance.

DSNL401E INDOUBT THREAD RESOLUTIONWITH COORDINATOR locationSHOWS HEURISTIC DAMAGE FORluwid=token - REMOTE ABORTVERSUS LOCAL COMMIT.INFORMATION RECORDED INTRACE RECORD WITH IFCID=207AND IFCID SEQUENCENUMBER=seq-no1 AND IN TRACERECORD WITH IFCID=203 ANDIFCID SEQUENCE NUMBER=seq-no2

ExplanationDb2 has participant responsibility in the logical unit ofwork identified by 'luwid=token'. Resolution with thecoordinator identified by 'location' shows heuristicdamage occurred. The Db2 thread representing thelogical unit of work was previously resolved with theRECOVER INDOUBT command. The action taken wasto commit the thread. Subsequently, communicationwas reestablished with the coordinator and resolutionshows that the coordinator aborted the thread.

• The application was told that commit failed.• Any resources updated at the coordinator were

rolled back.• Updated resources at this Db2 were committed.



• The requester's VTAM LU name (<luname>)

• The requester's IP address


seq-no1The IFCID sequence number associated with the207 trace record. The sequence number is printedin hexadecimal format. If the sequence number iszero, IFCID 207 was not active or it was active witha destination of the resident trace table only. IFCID207 is a member of statistics class 4, which has adefault destination of SMF. This trace record iswritten when the heuristic damage condition wasdetected and contains information about thedamage condition.

seq-no2The IFCID sequence number associated with the203 trace record. The sequence number is printedin hexadecimal format. If the sequence number iszero, IFCID 203 was not active or it was active witha destination of the resident trace table only. IFCID203 is a member of statistics class 4, which has adefault destination of SMF. This trace record waswritten when the heuristic decision to commit orabort was made and contains information aboutthe decision, including the names of anydownstream participants.


System programmer responseDetermine the destination of statistics class 4. Locateand print the trace record with SEQUENCENUMBER='seq-no1'. Call the database administrator.

Database Administrator Action: Correct the damage.This is not an easy task. Since the time of the heuristicaction, the data that was committed with theRECOVER INDOUBT command might have been usedby many applications - read and/or write. Correctingthe damage might involve reversing the effects ofthese applications as well. Tools available are:


• The DSN1LOGP utility provides a summary reportthat identifies the table spaces modified by thelogical unit of work, and any downstream participantlocations involved in the logical unit of work.




DSNL402I INDOUBT THREAD RESOLUTIONWITH PARTICIPANT locationSHOWS HEURISTIC DAMAGE FORluwid=token - REMOTE COMMITVERSUS LOCAL ABORT.INFORMATION RECORDED INTRACE RECORD WITH IFCID=207AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 has coordinator responsibility for the logical unitof work identified by 'luwid=token'. Resolution with aparticipant shows heuristic damage occurred. Theparticipant identified by 'location' manually resolvedthe indoubt thread identified by 'luwid=token'. Theaction taken was to commit the thread. This isinconsistent with the abort decision of the coordinator.

• The application was told that commit failed.• Any resources updated at the participant were

committed.• Updated resources at this Db2 were rolled back.





seq-noThe IFCID sequence number associated with thetrace record. The sequence number is printed inhexadecimal format. If the sequence number iszero, then IFCID 207 was not active or it wasactive with a destination of the resident trace tableonly. IFCID 207 is a member of statistics class 4,which has a default destination of SMF.

If the location specified refers to a Db2 for Linux,UNIX, and Windows system that is running at the DB29 level or later, and that server location has enabledaccess to non-Db2 databases through the Federated

Database or Information Integrator capability, thenany updates made to that downstream non-Db2database will be processed under the control of theDb2 for Linux, UNIX, and Windows unprotected updatecapability. This permits changes to be made to thisdownstream non-Db2 database, even when thechanges were being requested through applicationsrunning under two-phase commit or protected updatecontrol, such as CICS and IMS. During phase one ofcommit processing, the Db2 for Linux, UNIX, andWindows server will have actually committed thechanges to the downstream non-Db2 database by thetime it replies to this Db2 that it is prepared to accept acommit decision from. However, if during phase onecommit negotiation with other downstream databaseservers and other coordinated resource managersfrom CICS or IMS, the decision is made to abort theunit of work, this will result in heuristic damage to thedata at the non-Db2 database downstream of the Db2for Linux, UNIX, and Windows server. No attempts willbe made to resync with the identified remote locationserver, and a Db2 indoubt thread will not be left in Db2to reflect this issue.

System actionAlert A004 is generated. A trace record whoseIFCID=207 is written. Indoubt resolution with theparticipant completes.

System programmer responseCall the database administrator.

Database Administrator Action: Inform the databaseadministrator at 'location' that heuristic damageoccurred for the logical unit of work withLUWID='luwid'. Db2 was the coordinator for the logicalunit of work and made the decision to abort thedatabase updates made by 'luwid'. At 'location' aheuristic decision was made to COMMIT the updatesmade by 'luwid'.

Information about the heuristic damage continues toappear in the DISPLAY THREAD TYPE(INDOUBT)report until it is purged with the RESET INDOUBTcommand.

DSNL403I INDOUBT THREAD RESOLUTIONWITH PARTICIPANT locationSHOWS HEURISTIC DAMAGE FORluwid=token - REMOTE ABORTVERSUS LOCAL COMMIT.INFORMATION RECORDED INTRACE RECORD WITH IFCID=207AND IFCID SEQUENCENUMBER=seq-no


ExplanationDb2 has coordinator responsibility for the logical unitof work identified by 'luwid=token'. Resolution with aparticipant shows heuristic damage occurred. Theparticipant identified by 'location' manually resolvedthe indoubt thread identified by 'luwid=token'. Theaction taken was to abort the thread. This isinconsistent with the commit decision of thecoordinator.

• The application was told that commit succeeded.• Any resources updated at the participant were rolled

back.• Updated resources at this Db2 were committed.





seq-noThe IFCID sequence number associated with thetrace record. The sequence number is printed inhexadecimal format. If the sequence number iszero, IFCID 207 was not active or it was active witha destination of the resident trace table only. IFCID207 is a member of statistics class 4, which has adefault destination of SMF.

System actionAlert A004 is generated. A trace record with IFCID 207is written. Indoubt resolution with the participantcompletes.


Database Administrator Action: Inform the databaseadministrator at 'location' that heuristic damageoccurred for the logical unit of work withLUWID='luwid'. Db2 was the coordinator for the logicalunit of work and made the decision to COMMIT thedatabase updates made by 'luwid'. At 'location' aheuristic decision was made to back out (ABORT) theupdates made by 'luwid'.

Information about the heuristic damage continues toappear in the DISPLAY THREAD TYPE(INDOUBT)report until it is purged with the RESET INDOUBTcommand.

DSNL404E PROTOCOL ERROR DURINGINDOUBT THREAD RESOLUTIONWITH COORDINATOR locationLUWID=luwid=tokenINFORMATION RECORDED INTRACE RECORD WITH IFCID=206AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 has participant responsibility for the logical unit ofwork identified by 'luwid=token'. The Db2 threadassociated with the logical unit of work is indoubt. Aprotocol error occurred during indoubt resolution withthe coordinator identified by 'location'.location

Either the relational database name (location-name) or the logical unit name (<luname>) of thecoordinator.



System actionThe indoubt thread remains indoubt. Alert A003 isgenerated. A trace record whose IFCID=206 is written.

System programmer responseThis is an APARable error, probably at the coordinator,but possibly at the Db2 participant. The Db2documentation required is contained in the statisticsclass 4 trace record that was written. Determine thedestination of statistics class 4. Locate and print thetrace record with SEQUENCE NUMBER='seq-no'.

Call the database administrator.

Database Administrator Action: Db2 does notattempt to automatically resolve the indoubt thread.The indoubt thread must be manually resolved. Thecommit or abort decision made at the coordinatormust be determined so that the same decision can bemade at this participant Db2.

Contact the database administrator at the coordinatorlocation to determine whether the thread withLUWID=luwid committed or aborted.


If the coordinator system is another Db2, the followingsteps can be taken at the Db2 coordinator todetermine the commit or abort decision.

1. If the coordinator Db2 system is running and a Db2conditional restart was not performed since theerror was detected at this (the participant) location,ask the database administrator at the Db2coordinator location to issue one of the followingDISPLAY THREAD TYPE(INDOUBT) commands:

• A -DISPLAY THREAD TYPE(INDOUBT), using theLOCATION keyword and specifying the locationname of the local Db2.

• A -DISPLAY THREAD TYPE(INDOUBT)LUWID(luwid)

If a thread with LUWID=luwid appears in thedisplay, then the display also includes the commitor abort decision. If no thread with LUWID=luwidappears in the display, the thread was aborted.

2. If the Db2 coordinator is down, or if a conditionalrestart was performed there, ask the databaseadministrator at the Db2 coordinator to runDSN1LOGP, specifying SUMMARY(ONLY) FILTERLUWID(luwid). The output from DSN1LOGPincludes the commit or abort decision.

Use the RECOVER INDOUBT command at this (theparticipant) location to resolve the indoubt thread.

DSNL405I THREAD luwid=token PLACED ININDOUBT STATE BECAUSE OFCOMMUNICATION FAILURE WITHCOORDINATOR location.INFORMATION RECORDED INTRACE RECORD WITH IFCID=209AND IFCID SEQUENCENUMBER=seq-no

ExplanationDuring execution of the two phase commit protocolwith the coordinator identified by 'location',communication failed. Phase 1 of the protocolcompleted and the thread is prepared for eithercommit or abort.

The thread is placed in the indoubt state and appearsin a DISPLAY THREAD TYPE (INDOUBT) report.Periodic attempts are made to reestablishcommunication with the coordinator for automaticindoubt resolution. If successful, message DSNL407 orDSNL415 is written.luwid=token

The global logical unit of work id and the localtoken that identify the thread.





System actionAlert A006 is generated. A trace record whoseIFCID=209 is written.

Operator responseIf message DSNL407 or DSNL415 for the LUWIDspecified in the DSNL405 message does not appear ina reasonable amount of time, call the systemprogrammer.

System programmer responseDetermine the cause of the communication failure andhave the problem fixed. Db2 periodically attempts toreestablish communication. If the problem cannot befixed in a reasonable amount of time, call the databaseadministrator. Manual resolution of the indoubt threadmight be necessary to release locked resources.

Database Administrator Action: Take the followingactions to resolve this thread using manual means(that is, take heuristic action) if it is necessary torelease locks held by this thread.

• Determine the proper commit or abort decision bycontacting the database administrator at thecoordinator 'location' shown in this message in orderto determine whether the thread with LUWID=luwidcommitted or aborted.

If the coordinator system is another Db2, thefollowing steps can be taken at the Db2 coordinatorto determine the commit or abort decision.

1. If the coordinator Db2 system is running and aDb2 conditional restart was not performed sincethe error was detected at this (the participant)location, ask the database administrator at theDb2 coordinator location to issue one of thefollowing DISPLAY THREAD TYPE(INDOUBT)commands:


– A -DISPLAY THREAD TYPE(INDOUBT), usingthe LOCATION keyword and specifying thelocation name of the local Db2.

– A -DISPLAY THREAD TYPE(INDOUBT)LUWID(luwid)

If a thread with LUWID=luwid appears in thedisplay, then the display also includes the commitor abort decision. If no thread with LUWID=luwidappears in the display, then the thread wasaborted.

2. If the Db2 coordinator is down or if a conditionalrestart was performed there, ask the databaseadministrator at the Db2 coordinator to runDSN1LOGP, specifying SUMMARY(ONLY) FILTERLUWID(luwid). The output from DSN1LOGPincludes the commit or abort decision.

• Use the RECOVER INDOUBT command to commit orabort the thread.

DSNL406I THREAD luwid=token ATPARTICIPANT location MAY BEINDOUBT BECAUSE OF ACOMMUNICATION FAILURE. DB2COMMITTED THE THREAD.INFORMATION RECORDED INTRACE RECORD WITH IFCID=209AND IFCID SEQUENCENUMBER=seq-no

ExplanationDuring execution of the two phase commit protocolwith the participant identified by 'location',communications failed. Phase 1 of the protocolcompleted with the participant, which is prepared toeither commit or abort. The decision to commit thethread was made, but cannot be communicated to theparticipant at this time. The participant is indoubt.

Db2 becomes responsible for indoubt resolution withthe participant. This responsibility appears in aDISPLAY THREAD TYPE (INDOUBT) report. Periodicattempts are made to reestablish communication withthe participant for automatic indoubt resolution. Ifsuccessful, message DSNL423 is written.luwid=token







Operator responseIf message DSNL423 for the LUWID specified inmessage DSNL406 does not appear in a reasonableamount of time, call the system programmer.

System programmer responseDetermine the cause of the communication failure andhave the problem fixed. Db2 periodically attempts toreestablish communication. If the problem cannot befixed in a reasonable amount of time, call the databaseadministrator. The participant might need to manuallyresolve the indoubt state to release locked resources.

Database Administrator Action: If the unit of workwith LUWID=luwid is indoubt at 'location', inform thedatabase administrator there that the logical unit ofwork with LUWID=luwid was committed to assist inmanual resolution of the indoubt thread at 'location'.

DSNL407I AUTOMATIC RESOLUTION OFluwid=token WITH COORDINATORlocation RESULTED IN COMMIT

ExplanationThe identified indoubt logical unit of work wasautomatically resolved by communication with thecoordinator location. After automatic resolution, thismessage is issued if message DSNL405 was previouslyissued to report the thread as indoubt. This message isnot issued if message DSNL405 occurs in one restartof DDF or Db2, and automatic resolution occurs in adifferent restart of DDF or Db2.luwid=token

The global logical unit of work id and the localtoken that identify the thread



• The requester's VTAM LU name (<luname>)


• The requester's IP address


DSNL408I INDOUBT THREAD RESOLUTIONWITH COORDINATOR locationSHOWS HEURISTIC DAMAGE ATPARTICIPANT location FORluwid=token - COORDINATORCOMMIT VERSUS PARTICIPANTABORT. INFORMATION RECORDEDIN TRACE RECORD WITHIFCID=207 AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 has participant responsibility in the logical unit ofwork identified by 'luwid=token' for the coordinator atCOORDINATOR 'location' and coordinationresponsibility in the same logical unit of work for theparticipant at PARTICIPANT 'location'. Heuristicdamage occurred.

• The application was told that commit succeeded.• Any resources updated at the coordinator and at this

Db2 were committed.• Updated resources at the participant were rolled

back.







System programmer responseDetermine the destination of statistics class 4. Locateand print the trace record with SEQUENCENUMBER='seq-no'. Call the database administrator.

Database Administrator Action: Inform the databaseadministrator at the coordinator 'location' and at theparticipant 'location' of the problem.

Correcting the damage at the participant is not an easytask. Since the time of the heuristic action, the datathat was aborted using manual means might havebeen used by many applications - read and/or write.Correcting the damage might involve reversing theeffects of these applications as well. The followinginformation that is available at Db2 might be helpful incorrecting the problem:


• The DSN1LOGP utility provides a summary reportthat identifies the table spaces modified by thelogical unit of work at the local Db2 as well as anydownstream participant locations involved in thelogical unit of work. This information, while notdirectly related to the damage at the participant,might be useful in determining the scope of theproblem.



DSNL409I INDOUBT THREAD RESOLUTIONWITH COORDINATOR locationSHOWS HEURISTIC DAMAGE ATPARTICIPANT location FORluwid=token - COORDINATORABORT VERSUS PARTICIPANTCOMMIT. INFORMATIONRECORDED IN TRACE RECORDWITH IFCID 207 AND IFCIDSEQUENCE NUMBER=seq-no

ExplanationDb2 has participant responsibility in the logical unit ofwork identified by 'luwid=token' for the coordinator atCOORDINATOR 'location' and coordinationresponsibility in the same logical unit of work for theparticipant at PARTICIPANT 'location'. Heuristicdamage occurred.


• The application was told that commit failed.• Any resources updated at the coordinator and at this

Db2 were rolled back.• Updated resources at the participant were

committed.







System programmer responseDetermine the destination of statistics class 4. Locateand print the trace record with SEQUENCENUMBER='seq-no'. Call the database administrator.

Database Administrator Action: Inform the databaseadministrator at the coordinator 'location' and at theparticipant 'location' of the problem.

Correcting the damage at the participant is not an easytask. Since the time of the heuristic action, the datathat was committed using manual means might havebeen used by many applications - read and/or write.Correcting the damage might involve reversing theeffects of these applications as well. This informationis available at Db2 and might be helpful in correctingthe problem.


• The DSN1LOGP utility provides a summary reportthat identifies the table spaces modified by thelogical unit of work at the local Db2 and anydownstream participant locations involved in the

logical unit of work. This information, while notdirectly related to the damage at the participant,might be useful in determining the scope of theproblem.


Contact your IBM support center for furtherassistance.

DSNL410I WARM START CONNECTION BYPARTNER location REJECTED.PARTNER CHANGED AT LEAST 1OF - OUR LOG NAMEoldourname(newourname), THEIRLOG NAMEoldtheirname(newtheirname),PA_SUPPORT oldpa(newpa),FLAG_BYTE_SENT oldfb(newfb),CCLUNAME_SENToldccls(newccls), AND INDOUBTTHREADS REQUIRE RESOLUTION.SEE IFCID=205 TRACE RECORDWITH IFCID SEQUENCENUMBER=seq-no.

ExplanationAn attempt to make a warm start connection with apartner was rejected because the partner specified adifferent set of sync point parameters than the onesthat were in use when communications were lost. Db2has knowledge of indoubt threads that involve thepartner as either the coordinator or a participant. Thiserror might be a recoverable error if the partner canrestart with the original sync point parameters. If thisis not possible, then the partner must perform a coldstart connection with Db2.location

The 'location' with which the connection failed:either the relational database name (location-name) or the logical unit name (<luname>) of thepartner.

oldournameThe log name for this Db2 subsystem. This value isnull if the partner did not initiate the log nameexchange.

newournameThe log name for this Db2 subsystem, asremembered by our partner and sent to us in theattempted warm start connection. This value isnull if the partner did not initiate the log nameexchange.


oldtheirnameThe log name used by the partner during the lastconnection, as remembered by Db2.

newtheirnameThe log name used by the partner in the attemptedwarm start connection.

oldpaThe sync point protocol used during the lastconnection, as remembered by the Db2 (PA -Presumed Abort, PN - Presumed Nothing).

newpaThe sync point protocol used during the lastconnection, as remembered by the partner (PA -Presumed Abort, PN - Presumed Nothing).

oldfbThe use of the PS header byte 2 during the lastconnection, as remembered by Db2 (F - used asflag byte, N - not used as flag byte).

newfbThe use of the PS header byte 2 during the lastconnection, as remembered by the partner (F -used as flag byte, N - not used as flag byte).

oldcclsWhether the luname of the conversation correlatorwas exchanged as part of the sync point protocolduring the last connection, as remembered byDb2. (E - was exchanged, N - was not exchanged).

newcclsWhether the luname of the conversation correlatorwas exchanged as part of the sync point protocolduring the last connection, as remembered by thepartner (E - was exchanged, N - was notexchanged).


System actionThe connection with the partner is rejected. Alert A002is generated. Db2 retains indoubt knowledge.


Database Administrator Action: Contact thedatabase administrator at the partner 'location' anddetermine if it is possible for the partner to perform awarm start with same sync point parameters as ours

('oldourname', 'oldtheirname', 'oldpa', 'oldfb', 'oldccls').If this is possible, the next attempt to connect willsucceed.

If this cannot be done, then there are two otherpossible solutions:

• Have the partner 'location' perform a cold startconnection with this Db2 subsystem.

• Use the RESET INDOUBT command with the FORCEoption in conjunction with the LOCATION parameterto cause the next connection with the partner to be acold start connection.

DSNL411E COLD START CONNECTION BYCOORDINATOR locationACCEPTED. INDOUBT THREADSNEED MANUAL RESOLUTION.INFORMATION RECORDED INTRACE RECORD WITH IFCID=204AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 has participant responsibility for indoubt threads.The coordinator informed Db2 that it performed a coldstart operation and lost all knowledge of indoubtthreads. The indoubt threads at this Db2 must bemanually resolved with the RECOVER INDOUBTcommand.





This condition can falsely occur if the DDFcommunications database (CDB) contains definitionsthat allow a subsystem to remotely access itselfthrough SNA. To avoid this false condition, removeself-referencing CDB definitions.

System actionThe connection with the partner is accepted. AlertA001 is generated. A trace record whose IFCID=204 iswritten.



Database Administrator Action: Db2 is a participantwith one or more indoubt threads where thecoordinator is 'location'. The DBMS at 'location'performed a cold start. The Db2 participant assumesthat the coordinator recovery log was lost or damagedand indoubt thread resolution cannot be achieved.There is probably inconsistent data at the coordinator.A list of indoubt threads involving the coordinator'location' can be displayed using the DISPLAY THREADcommand for indoubt type threads by including theLOCATION('location') parameter in the command.

The heuristic decision (that is, to commit or abort thelogical unit of work) should be coordinated with anyother participants. The existence of other participantsmight not be easy to determine. The information mightbe available in the coordinators recovery log eventhough the coordinator performed a cold start. If thecoordinator is a Db2, then it might be possible toexecute the DSN1LOGP utility to produce a summaryreport. If this is possible, the following informationmight be produced:

• The LUWID of the thread.• The NID used by IMS or CICS to identify the thread.• The name of all participants.• The name of an upstream coordinator if the

coordinator is also a participant. This could happenwhen an application requester accesses a Db2 ASusing application-directed access, which in turnaccesses another Db2 server with system-directedaccess. (The local Db2 might be the third system inthis scenario.)

At this Db2 participant, all indoubt threadscoordinated by the cold starting location must beresolved with the RECOVER INDOUBT command.Locked data remains unavailable until resolution.Threads that were already resolved with this commandare discarded. Threads not yet resolved are discardedafter resolution with the command.

The commit or abort decision provided using theRECOVER INDOUBT command for a logical unit ofwork are propagated to all downstream participants, ifany.

DSNL412I PROTOCOL ERROR DETECTED INSYNCPOINT REQUEST/RESPONSEFROM COORDINATOR locationLUWID=luwid=token.INFORMATION RECORDED INTRACE RECORD WITH IFCID=208AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 is a participant in the logical unit of workidentified by 'luwid=token'. A protocol error occurredduring the SNA sync point exchange with thecoordinator identified by 'location'. The protocol errorfits into one of the following categories:

• An unknown SNA PS header was received.• An SNA PS header was received in the wrong

sequence.• An invalid LU6.2 verb sequence was used to deliver

the SNA PS header.• A DEALLOCATE TYPE(ABEND_SVC) was received

from the coordinator, indicating that the coordinatordetected a protocol violation in the PS headerstransmitted by Db2.

locationEither the relational database name (location-name) or the logical unit name (<luname>) of thecoordinator.



If the protocol error was detected before the commitdecision, the unit of work at the Db2 system might beindoubt. Db2 does not automatically resolve such anindoubt thread.

If the protocol error was detected after the commitdecision, the unit of work either completed commit orabort processing.


System programmer responseThis is an APARable error, probably at the coordinator,but possibly at Db2. The Db2 documentation requiredis contained in the statistics class 4 trace record.Determine the destination of statistics class 4. Locateand print the trace record with SEQUENCENUMBER='seq-no'.

The database administrator might need to manuallyresolve the indoubt thread.


Database Administrator Action: Determine if the'luwid' is indoubt by using the DISPLAY THREADcommand for type indoubt threads and including theLUWID('token') parameter in the command. If thethread is indoubt, it must be manually resolved usingthe RECOVER INDOUBT command. The commit orabort decision made at the coordinator must bedetermined so that the same decision can be made atDb2.

Contact the database administrator at the coordinatorlocation to determine whether the thread withLUWID=luwid committed or aborted.

If the coordinator system is another Db2, then thefollowing steps can be taken at the Db2 coordinator todetermine the commit or abort decision.

1. If the coordinator Db2 system is running and a Db2conditional restart was not performed since theerror was detected at this (the participant) location,ask the database administrator at the Db2coordinator location to issue one of the followingDISPLAY THREAD TYPE(INDOUBT) commands:

• A -DISPLAY THREAD TYPE(INDOUBT), using theLOCATION keyword and specifying the locationname of the local Db2.

• A -DISPLAY THREAD TYPE(INDOUBT)LUWID(luwid)

If a thread with LUWID=luwid appears in thedisplay, then the display also includes the commitor abort decision. If no thread with LUWID=luwidappears in the display, then the thread wasaborted.

2. If the Db2 coordinator is down or if a conditionalrestart was performed there, ask the databaseadministrator at the Db2 coordinator to runDSN1LOGP, specifying SUMMARY(ONLY) FILTERLUWID(luwid). The output from DSN1LOGPincludes the commit or abort decision.

DSNL413I PROTOCOL ERROR DETECTED INSYNCPOINT REQUEST/RESPONSEFROM PARTICIPANT locationLUWID=luwid=token.INFORMATION RECORDED INTRACE RECORD WITH IFCID=208AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 is the coordinator of the logical unit of workidentified by 'luwid=token'. A protocol error occurredduring the SNA sync point exchange with theparticipant identified by 'location'. The protocol errorfits into one of the following categories:

• An unknown SNA PS header was received.• An SNA PS header was received in the wrong

sequence.• An invalid LU6.2 verb sequence was used to deliver

the SNA PS header.• A DEALLOCATE TYPE(ABEND_SVC) was received

from the participant, indicating that the participantdetected a protocol violation in the PS headerstransmitted by Db2.

locationThe relational database name (location-name) ofthe participant.



If the protocol error is detected before the commitdecision, the unit of work is backed out.

If the protocol error is detected after the commitdecision, the outcome of the unit of work isunchanged. In this case, the remote participant mightbe indoubt. Db2 does not automatically resolve theindoubt thread with the partner 'location' after aprotocol error is detected.


System programmer responseThis is an APARable error, probably at the participant,but possibly at the Db2 coordinator. The Db2documentation required is contained in the statisticsclass 4 trace record. Determine the destination ofstatistics class 4. Locate and print the trace recordwith SEQUENCE NUMBER='seq-no'.

Call the database administrator. The participant mightneed to manually resolve the indoubt thread.

Database Administrator Action: The Db2 coordinatordoes not know the status of the thread at theparticipant. The Db2 coordinator assumes that it isindoubt and maintains knowledge of the indoubtparticipant until it is purged with the RESET INDOUBTcommand. If the thread is indoubt at the participant, it


must be resolved using manual (heuristic) means. Thestatus of the thread at the local Db2 (the coordinator)can be determined with the DISPLAY THREADcommand for type indoubt threads by including theLUWID('token') parameter in the command.

If the 'participant' location is also a Db2, the RECOVERINDOUBT command can be used at the participant toresolve the indoubt thread.

DSNL414E PROTOCOL ERROR DURINGINDOUBT THREAD RESOLUTIONWITH PARTICIPANT locationLUWID=luwid=tokenINFORMATION RECORDED INTRACE RECORD WITH IFCID=206AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 has coordinator responsibility for the logical unitof work identified by 'luwid=token'. The Db2 threadassociated with the logical unit of work is eithercommitted or aborted. A protocol error occurredduring indoubt resolution with the participantidentified by 'location'.

The thread at the participant remains indoubt. Db2rejects further attempts to automatically resolve theindoubt thread.location

The relational database name (location-name) ofthe participant.




System programmer responseThis is an APARable error, probably at the participant,but possibly at the Db2 coordinator. The Db2documentation required is contained in the statisticsclass 4 trace record. Determine the destination of

statistics class 4. Locate and print the trace recordwith SEQUENCE NUMBER='seq-no'.

Call the database administrator. The participant mightneed to manually resolve the indoubt thread.

Database Administrator Action: The Db2 coordinatormaintains knowledge of the indoubt participant until itis purged with the RESET INDOUBT command. If thethread is indoubt at the participant, it must bemanually (heuristically) resolved. The status of thethread at the local Db2 (the coordinator) can bedetermined with the DISPLAY THREAD command fortype indoubt threads by including the LUWID('token')parameter in the command.

If the participant is another Db2, the RECOVERINDOUBT command can be used to resolve theindoubt thread.

DSNL415I AUTOMATIC RESOLUTION OFluwid=token WITH COORDINATORlocation RESULTED IN ABORT

ExplanationThe identified indoubt logical unit of work wasautomatically resolved by communication with thecoordinator location. After automatic resolution, thismessage is issued if message DSNL405 was previouslyissued to report the thread as indoubt. This message isnot issued if message DSNL405 occurs in one restartof DDF or Db2, and automatic resolution occurs in adifferent restart of DDF or Db2.luwid=token






DSNL416I COLD START CONNECTIONREJECTED BY PARTNER location

ExplanationDb2 attempted to make a cold-start connection with apartner location. The partner rejected this attemptedconnection. Db2 never rejects cold-start connectionsby partners.


locationEither the relational database name (location-name) or the logical unit name (<luname>) of thepartner.

System actionThe connection was not made.


Database Administrator Action: Db2 is not able toconnect the partner 'location' until the partner'location' allows a cold-start connection with Db2.Contact the database administrator at the partner'location'.

Contact IBM Support for further assistance.

DSNL417E csect-name COLD STARTDETECTED AT COORDINATORLOCATION location FOR INDOUBTTHREAD WITH luwid=token.MANUAL RESOLUTION ISREQUIRED. INFORMATIONRECORDED IN TRACE RECORDWITH IFCID=204 and IFCSEQUENCE NUMBER=seq-no.

ExplanationDb2 has resync responsibility for the indoubt threadidentified. The partner location informed Db2 that ithad performed a cold start operation and lost allknowledge of this indoubt thread. This indoubt threadmust be manually resolved with the RECOVERINDOUBT command, followed by the RESET INDOUBTcommand.location

This field contains one of the following:



luwid=tokenThe logical unit of work id and the local token thatidentify the thread.

seq-noThe IFCID sequence number associated with thetrace record. The sequence number is printed inhexadecimal format. If the sequence number iszero, then IFCID 204 was not active or it wasactive with a destination of the resident trace tableonly. IFCID 204 is a member of statistics class 4,

which has a default destination of SMF andcontains information about a partner's cold start.



Database Administrator Action: Db2 is a participantwith one or more indoubt threads where thecoordinator is 'location'. The DBMS at 'location'performed a cold start. The Db2 participant assumesthat the coordinator recovery log was lost or damagedand indoubt thread resolution cannot be achieved.There may be inconsistent data at the coordinator. Alist of indoubt threads involving the coordinator'location' can be displayed using the DISPLAY THREADcommand for indoubt type threads by including theLOCATION('location') parameter in the command.

The heuristic decision (that is, to commit or abort thelogical unit of work) should be coordinated with anyother participants. The existence of other participantsmight not be easy to determine. The information mightbe available in the coordinators recovery log eventhough the coordinator performed a cold start. If thecoordinator is a Db2, then it might be possible toexecute the DSN1LOGP utility to produce a summaryreport. If this is possible, the following informationmight be produced:

• The LUWID of the thread.• The NID used by IMS or CICS to identify the thread.• The name of all participants.• The name of an upstream coordinator if the

coordinator is also a participant. This could happenwhen an application requester accesses a Db2 ASusing application-directed access, which in turnaccesses another Db2 server with system-directedaccess. (The local Db2 might be the third system inthis scenario.)

At this Db2 participant, all indoubt threadscoordinated by the cold starting location must beresolved with the RECOVER INDOUBT command.Locked data remains unavailable until resolution.Threads that were already resolved with this commandare discarded. Threads not yet resolved are discardedafter resolution with the command.

The commit or abort decision provided using theRECOVER INDOUBT command for a logical unit ofwork are propagated to all downstream participants, ifany.


DSNL418E csect-name COLD STARTDETECTED AT PARTICIPANTLOCATION location FOR INDOUBTTHREAD WITH luwid=token.POSSIBLE DAMAGE.INFORMATION RECORDED INTRACE RECORD WITH IFCID=204and IFC SEQUENCE NUMBER=seq-no.

ExplanationDb2 has coordinator responsibility for the indoubtthread identified. The partner location informed Db2that it had performed a cold start operation and lost allknowledge of this indoubt thread. There might bedamage at the participant.location








Database Administrator Action: Db2 is thecoordinator with indoubt thread resolutionresponsibility for one or more indoubt logical units ofwork at 'location'. The DBMS at 'location' performed acold start. Db2 assumes that the participant recoverylog was lost or damaged and indoubt thread resolutioncannot be achieved. There is probably inconsistentdata at the participant. Minimally, the participant mightnot completely reflect the final outcome of the threadsthat were indoubt at the time the failure occurred. Alist of indoubt threads involving the partner 'location'can be displayed using the DISPLAY THREAD

command for type indoubt threads by including theLOCATION('location) parameter in the command.

Information about the indoubt participant continues toappear in the DISPLAY THREAD TYPE(INDOUBT)report until it is purged with the RESET INDOUBTcommand.

DSNL419I PARTNER location HAS RESOLVEDWARM START STATUS ANDCONNECTION IS ACCEPTED

ExplanationA successful warm start connection was made with apartner. A previous attempt to make a warm startconnection with the partner was rejected with aDSNL410I message because the partner specified anincorrect log name.location

Either the relational database name (location-name) or the logical unit name (<luname>) of thepartner

System actionThe connection was successful. Normal processingcontinues.

DSNL420I COLD START CONNECTION BYPARTICIPANT location ACCEPTED.POSSIBLE DAMAGE.INFORMATION RECORDED INTRACE RECORD WITH IFCID=204AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 has coordinator responsibility for indoubt threadsat a participant and just connected with theparticipant, which lost all knowledge of indoubtthreads because of a previous cold start. There mightbe damage at the participant.location




seq-noThe IFCID sequence number associated with thetrace record. The sequence number is printed inhexadecimal format. If the sequence number iszero, then IFCID 204 was not active or it wasactive with a destination of the resident trace table


only. IFCID 204 is a member of statistics class 4,which has a default destination of SMF.

System actionThe connection with the partner is accepted. AlertA001 is generated. A trace record whose IFCID=204 iswritten.


Database Administrator Action: Db2 is thecoordinator with indoubt thread resolutionresponsibility for one or more indoubt logical units ofwork at 'location'. The DBMS at 'location' performed acold start. Db2 assumes that the participant recoverylog was lost or damaged and indoubt thread resolutioncannot be achieved. There is probably inconsistentdata at the participant. Minimally, the participant mightnot completely reflect the final outcome of the threadsthat were indoubt at the time the failure occurred. Alist of indoubt threads involving the partner 'location'can be displayed using the DISPLAY THREADcommand for type indoubt threads by including theLOCATION('location) parameter in the command.

Information about the indoubt participant continues toappear in the DISPLAY THREAD TYPE(INDOUBT)report until it is purged with the RESET INDOUBTcommand.

DSNL421I SNA XLN PROTOCOL VIOLATIONBY PARTNER location.INFORMATION RECORDED INTRACE RECORD WITH IFCID=0236AND IFCID SEQUENCENUMBER=seq-no

ExplanationDb2 detected a protocol violation in the SNA ExchangeLog Names (XLN) exchange with the partner at thespecified location.location

Either the relational database name (location-name) or the logical unit name (<luname>) of thepartner that sent the invalid XLN message.


System actionThe attempt to connect with the remote site fails. Db2writes a trace record with IFCID 0236.

Operator responseCall the system programmer.

System programmer responseContact the system programmer for the remote site.The invalid XLN message is recorded in the IFCID0236 trace record. The system logic error that causesthe invalid XLN message must be corrected at theremote site.

DSNL422I WARM START CONNECTION BYPARTNER location REJECTEDBECAUSE THE PARTNERREMEMBERS OUR LOG NAMEINCORRECTLY. OUR LOG NAME ISname1 AND THE PARTNERREMEMBERS IT AS name2

ExplanationAn attempt to make a warm start connection with apartner was rejected because the partner specified ourlog name as name2. Our log name is name1, which isthe LUNAME of the local Db2. This error might be arecoverable error if the partner can restart with our logname as name1. If this is not possible, then thepartner must perform a cold start connection withDb2.location

The 'location' with which the connection failed:either the relational database name (location-name) or the logical unit name (<luname>) of thepartner.

name1Our log name, as remembered by us.

name2Our log name, as remembered by our partner andsent to us in the attempted warm start connection.

System actionThe connection with the partner is rejected. Db2retains indoubt knowledge.


Database Administrator Action: Contact thedatabase administrator at the partner 'location' anddetermine if it is possible for the partner to perform a


warm start with our log name specified as the LUNAMEof this Db2. If this is possible, the next attempt toconnect will succeed.

If this cannot be done, then there are two otherpossible solutions.

• Have the partner 'location' perform a cold startconnection with this Db2 subsystem.

• Use the RESET INDOUBT command with the FORCEoption in conjunction with the LOCATION parameterto cause the next connection with the partner to be acold start connection.

DSNL423I AUTOMATIC RESOLUTION OFluwid=token WITH PARTICIPANTlocation RESULTED IN COMMIT

ExplanationThe identified indoubt logical unit of work wasautomatically resolved through communication withthe participant location. After automatic resolution,this message is issued if message DSNL406 waspreviously issued reporting the thread as indoubt. Thismessage is not issued if message DSNL406 occurs inone restart of DDF or Db2, and automatic resolutionoccurs in a different restart of DDF or Db2.luwid=token






DSNL424I AUTOMATIC RESOLUTION OFluwid=token WITH PARTICIPANTlocation RESULTED IN ABORT

ExplanationThe identified indoubt logical unit of work wasautomatically resolved by communication with theparticipant location. After automatic resolution, thismessage is issued if message DSNL425 was previouslyissued reporting the thread as being indoubt. Thismessage is not issued if message DSNL425 occurs inone restart of DDF or Db2, and automatic resolutionoccurs in a different restart of DDF or Db2.

luwid=tokenThe global logical unit of work id and the localtoken that identify the thread





DSNL425I THREAD luwid=token ATPARTICIPANT location MAY BEINDOUBT BECAUSE OF ACOMMUNICATION FAILURE. DB2ABORTED THE THREAD.INFORMATION RECORDED INTRACE RECORD WITH IFCID=209AND IFCID SEQUENCENUMBER=seq-no

ExplanationDuring execution of the two phase commit protocolwith the participant identified by 'location',communications failed. Phase 1 of the protocolcompleted with the participant and it is prepared foreither commit or abort. The decision to abort thethread was made, but cannot be communicated to theparticipant at this time. The participant is indoubt.

Db2 becomes responsible for indoubt resolution withthe participant. This responsibility appears in aDISPLAY THREAD TYPE (INDOUBT) report. Periodicattempts are made to reestablish communication withthe participant for automatic indoubt resolution. Ifsuccessful, message DSNL424 is written.luwid=token





seq-noThe IFCID sequence number associated with thetrace record. The sequence number is printed inhexadecimal format. If the sequence number iszero, IFCID 209 was not active or it was active witha destination of the resident trace table only. IFCID


209 is a member of statistics class 4, which has adefault destination of SMF.


Operator responseIf message DSNL424 for the LUWID specified inmessage DSNL406 does not appear in a reasonableamount of time, call the system programmer.

System programmer responseDetermine the cause of the communication failure andhave the problem fixed. Db2 periodically attempts toreestablish communication. If the problem cannot befixed in a reasonable amount of time, call the databaseadministrator. The participant might need to resolvethe indoubt state manually in order to release lockedresources.

Database Administrator Action: If the unit of workwith LUWID=luwid is indoubt at 'location', inform thedatabase administrator there that the logical unit ofwork with LUWID=luwid was aborted to assist inmanual resolution of the indoubt thread at 'location'.

DSNL429I INCONSISTENT DDF LOG DATA,THE FIRST CONNECTION WITHEACH REMOTE LOCATION WILL BEA COLD START CONNECTION

ExplanationDb2 detected an inconsistency in the Db2 log duringrestart operations. Since the log is inconsistent andcannot be trusted, Db2 performs a cold startconnection with each partner LU the next time aconnection with that LU is attempted. If Db2 hasindoubt resolution responsibility either as acoordinator or as a participant, then this information islost as indicated by messages DSNL438 and/orDSNL439, which might follow this message. Thismeans that:

• All information that Db2 maintained about havingcoordinator responsibility for remote participantswas purged. These remote participants need manualresolution for any indoubt threads for which Db2 wasthe coordinator. A DSNL439I message is displayedfor each indoubt remote participant.

• All information that Db2 maintained about havingparticipant responsibility for remote coordinatorswas purged. A DSNL438I message is displayed foreach database access thread that has a remotecoordinator. If a database access thread remains

indoubt at the end of restart, then the thread mustbe manually resolved. A -DISPLAY THREAD (*)TYPE(INDOUBT) LOCATION (*) command provides areport that lists the indoubt threads that needmanual resolution.



Database Administrator Action: See the DSNL438Iand DSNL439I messages to determine what action totake.

DSNL432I DDF IS COORDINATOR FOR nnnnTHREADS WITH mmmm INDOUBTREMOTE PARTNERS

ExplanationThis message is issued when DDF is started orstopped, if DDF determines that this Db2 hascoordinator responsibility for one or more indoubtthreads with one or more partners. This is a summarystatus message.nnnn

The number of indoubt threads for which Db2 isthe coordinator

mmmmThe number of remote partners where the threadsare indoubt


Operator responseIf the message was issued as a result of DDF starting,no action is necessary. If the message was issued as aresult of DDF stopping, contact the databaseadministrator.

Database Administrator Action: If the message wasissued as a result of stopping DDF, then Db2maintained all information necessary to performautomatic resynchronization with partner locationsand resolve all indoubt units of work. Issue the STARTDDF command to initiate this process.

If the message was issued as a result of starting DDF,then DDF started automatic resynchronization.


DSNL433I DDF IS PARTICIPANT FOR nnnnINDOUBT THREADS WITH mmmmREMOTE PARTNERS

ExplanationThis message is issued when DDF is started orstopped, if DDF determines that this Db2 hasparticipant responsibility for one or more indoubtthreads with one or more partners. This is a summarystatus message.nnnn

The number of indoubt threads for which Db2 isthe participant

mmmmThe number of remote partners that havecoordinator responsibility


Operator responseIf the message was issued as a result of DDF starting,no action is necessary. If the message was issued as aresult of DDF stopping, contact the databaseadministrator.

Database Administrator Action: If the message wasissued as a result of stopping DDF, then Db2maintained all information necessary to performautomatic resynchronization with partner locationsand resolve all indoubt units of work. Issue the STARTDDF command to initiate this process.

If you do not want to perform automaticresynchronization, you can still resolve the indoubtunits of work for which Db2 is a participant and whichhold database resources locked. Use the DISPLAYTHREAD command for type indoubt threads toproduce a display that lists these threads. Then usethe RECOVER INDOUBT command to either commit orabort these units of work.

To avoid data inconsistency, coordinate this manualresolution with the database administrators at thelocations that have coordinator responsibility for eachindoubt unit of work. If any of the indoubt units of workat Db2 also have coordinator responsibility forparticipant locations, then you should notify thedatabase administrators at the participant locations ofthe commit or abort decision so they can make thesame decision.

DSNL434E DDF NOT STARTED - INCORRECTVTAM RELEASE LEVEL

ExplanationThe local VTAM release level is older than theminimum release level required by Db2. When Db2issues the VTAM OPEN macro, the VTAM release levelis returned to Db2. Db2 examines the VTAM releaselevel to determine whether the local VTAM systemprovides the function required by Db2.

System actionThe attempt to START DDF fails.

Operator responseCall the system programmer.

System programmer responseInstall a release of VTAM that is compatible with theDb2 system. The Db2 Program Directory identifies therequired VTAM release level.

DSNL438I RESYNC STATUS PURGED FORCOORDINATOR location.LUWID=luwid, URID=urid,STATUS=s INFORMATIONRECORDED IN TRACE RECORDWITH IFCID=235 and IFCIDSEQUENCE NUMBER=seq-no

ExplanationThe information related to resynchronization with theremote coordinator location for the logical unit of workidentified by 'luwid', which is displayed in thismessage, is being purged by Db2. Automatic indoubtresolution responsibility for this distributed logical unitof work can no longer be performed.

This situation can arise in one of two ways;

• A Db2 conditional restart (other than a Db2 coldstart; that is, a Db2 conditional restart withSTARTRBA=ENDRBA) is being performed.

• An inconsistency in the Db2 log was detected duringDb2 restart processing (indicated by a DSNL429Imessage).




luwidThe global logical unit of work id that identifies thelogical unit of work.


uridThe unit of recovery identifier. This is the RBA onthe Db2 recovery log of the log record that marksthe beginning of the logical unit of work. This is theearliest RBA required to process the logical unit ofwork during restart.

sRestart status of the logical unit of work. WhenDb2 came down, the logical unit of work was inone of these states:A

INABORT: The logical unit of work was in the"must-complete" phase of abort, but abort hasnot yet completed.

CINCOMMIT: The logical unit of work was in the"must-complete" phase of commit, but commithas not yet completed.

DINDOUBT: The logical unit of work completedthe first phase of commit, but Db2 has not yetreceived the commit or abort decision from thecoordinator.

FINFLIGHT: The logical unit of work has not yetcompleted the first phase of commit andshould be backed out.

UUNKNOWN: The status of the logical unit ofwork is not known to Db2 because ofconditional restart.

seq-noThe IFCID sequence number associated with thetrace record. The trace record is written tostatistics class 4, which is started to SMF as adefault during Db2 installation. Statistics class 4must be started to a permanent destination (SMFor GTF) for the trace record to be accessible. Thesequence number is printed in hexadecimal.



Database Administrator Action: Theresynchronization information that was purged by Db2is recorded in this message. To determine the propercommit or abort decision made by the coordinator at'location', use the status code as follows:

AThe correct decision is to abort the logical unit ofwork.

CThe correct decision is to commit the logical unit ofwork.

DContact the database administrator at 'location' todetermine the correct decision.

FThe correct decision is to abort the logical unit ofwork.

UContact the database administrator at 'location' todetermine the correct decision.

DSNL439I RESYNC STATUS PURGED FORPARTICIPANT location.LUWID=luwid, URID=urid,STATUS=s INFORMATIONRECORDED IN TRACE RECORDWITH IFCID=235 and IFCIDSEQUENCE NUMBER=seq-no

ExplanationDb2 is purging the information related toresynchronization with the remote participant locationfor the logical unit of work identified by 'luwid', whichis displayed in this message. Automatic indoubtresolution responsibility for this distributed logical unitof work can no longer be performed.

This situation can arise in one of two ways:

• A Db2 conditional restart (other than a Db2 coldstart; that is, a Db2 conditional restart withSTARTRBA=ENDRBA) is being performed.

• An inconsistency in the Db2 log was detected duringDb2 restart processing (indicated by a DSNL429Imessage).




luwidThe global logical unit of work id that identifies thelogical unit of work.

uridThe unit of recovery identifier. This is the RBA onthe Db2 recovery log of the log record that marksthe beginning of the logical unit of work. This is the


earliest RBA required to process the logical unit ofwork during restart.

sRestart status of the logical unit of work. WhenDb2 came down, the logical unit of work was inone of these states:A

INABORT: The logical unit of work was in the"must-complete" phase of abort, but abort hasnot yet completed.

CINCOMMIT: The logical unit of work was in the"must-complete" phase of commit, but commithas not yet completed.

DINDOUBT: The logical unit of work completedthe first phase of commit, but Db2 has not yetreceived the commit or abort decision from thecoordinator.

FINFLIGHT: The logical unit of work has not yetcompleted the first phase of commit andshould be backed out.

UUNKNOWN: The status of the logical unit ofwork is not known to Db2 because ofconditional restart.

seq-noThe IFCID sequence number associated with thetrace record. The trace record is written tostatistics class 4, which is started to SMF as adefault during Db2 installation. Statistics class 4must be started to a permanent destination (SMFor GTF) for the trace record to be accessible. Thesequence number is printed in hexadecimal.



Database Administrator Action: Theresynchronization information that was purged by Db2is recorded in this message. When communicating theproper commit or abort decision to the databaseadministrator at 'location', use the status code asfollows:A

Abort the logical unit of work.C

Commit the logical unit of work.

DSee the DSNL438I message produced for the same'luwid' and 'urid' to determine the coordinator'location'. Contact the database administrator at'location' to determine the correct decision.

FAbort the logical unit of work.

UIf there is a DSNL438I message for the same'luwid' and 'urid', proceed as described aboveunder 'D'. Otherwise, there might be informationavailable on the Db2 log that a DSN1LOGPsummary report can provide. If this is notsuccessful, contact IBM Support.

DSNL440I csect-name RESET INDOUBTCOMMAND SPECIFICATION INERROR

ExplanationA RESET INDOUBT command was issued, but thespecification of keywords or keyword parametervalues was in error.

System actionNo indoubt information was purged. Systemprocessing continues normally.

User responseOne of the following errors was made in the RESETINDOUBT command specification:

• RESET INDOUBT was issued without any otherkeywords specified. At least one of the followingkeywords must also be specified: LUNAME, IPADDR,LOCATION, or LUWID.

• RESET INDOUBT was issued with both the LUWIDand LOCATION keywords specified, but a list ofLOCATION keyword parameter values was specified.When both the LUWID and LOCATION keywords arespecified only one LOCATION keyword parametervalue is allowed.

• RESET INDOUBT was issued with at least oneLOCATION keyword parameter value that began witha '<', but did not end with a '>', or the length of thebracketed value was not 1 to 8 characters. When theLOCATION keyword parameter value is specified inthe <luname> format, the luname value must bebracketed with '<' and '>' and be 1 to 8 characterslong.

• RESET INDOUBT was issued with an invalid IPADDRkeyword parameter. Verify that the specifiedIPADDRs are in the proper form, that there is a


double period delimiter (..) between the IPADDR andport, and that the port number is valid.

If needed, issue the DISPLAY THREADTYPE(INDOUBT) command to display information(including LOCATION, LUWID, and LUNAME values)about all indoubt threads. Correct the RESET INDOUBTcommand specification, and reissue the command.

DSNL441I KEYWORD 'LUWID' PARAMETERVALUE parmvalue FORMAT INERROR

ExplanationA RESET INDOUBT command with the LUWIDparameter was issued, but the specified parametervalue (parmvalue) has an invalid format for an LUWID.There are two correct formats for the LUWIDparameter. The first correct format is called a token,and is a 1 to 5 digit decimal number. The secondcorrect format is 'netid.luname.luwunique.comseq',where:netid

A 1 to 8 character network IDluname

A 1 to 8 character lunameluwunique

A 12 character hexadecimal numbercomseq

A 4 character hexadecimal number

All fields in the second correct format must beseparated by a period (.) delimiter.

System actionIndoubt information about the specified logical unit ofwork is not purged from the system.

User responseTo determine the correct LUWID value for the unit ofwork indoubt information that you want to purge, issuethe DISPLAY THREAD TYPE(INDOUBT) command todisplay all units of work for which indoubt informationexists. Then reissue the RESET INDOUBT command,specifying the correct LUWID parameter value.

DSNL442I QUALIFYING INDOUBTINFORMATION FOR LOCATIONlocation NOT FOUND

ExplanationA -RESET INDOUBT LOCATION('location') commandwas issued, but Db2 has no indoubt information aboutthe specified location.

locationThe value specified after the LOCATION keyword inthe RESET INDOUBT command.


User responseUse the -DISPLAY THREAD(*) TYPE(INDOUBT)LOCATION(*) command to list the locations for whichDb2 has indoubt information. After determining thecorrect location, reissue the command.

DSNL443I QUALIFYING INDOUBTINFORMATION FOR LUWID=valueNOT FOUND

ExplanationA -RESET INDOUBT LUWID('value') command wasissued where 'value' is either an luwid or the localtoken that represents an luwid. Either Db2 has noindoubt information about the specified luwid ortoken, or Db2 has indoubt information that cannot bepurged using the -RESET INDOUBT command with theLUWID option.value

The global logical unit of work id or the local tokenthat was specified for the LUWID keyword in theRESET INDOUBT command.


User responseUse the -DISPLAY THREAD(*) TYPE(INDOUBT)LOCATION(*) command to list the indoubt informationknown to Db2. If the -DISPLAY THREAD output doesnot include information about the specified luwid, thenthat is the reason the message was issued. If the -DISPLAY THREAD output does include informationabout the specified luwid, this information cannot bepurged using the -RESET INDOUBT command with theLUWID option. Refer to the description of eachmessage produced by the -DISPLAY THREAD outputthat relates to the specified luwid in order todetermine how to proceed. After determining thecorrect luwid or token, reissue the command.

DSNL444I QUALIFYING INDOUBTINFORMATION FOR LOCATIONlocation HAS BEEN PURGED


ExplanationA -RESET INDOUBT LOCATION('location') commandissued to purge indoubt information about the namedlocation completed successfully and the indoubtinformation was purged.location

Either the relational database name (location-name) or the logical unit name (<luname>) thatwas specified after the LOCATION keyword on theRESET INDOUBT command.

System actionThe specified indoubt information was purged. Systemprocessing continues normally.

DSNL445I QUALIFYING INDOUBTINFORMATION FOR LUWID valueHAS BEEN PURGED

ExplanationA -RESET INDOUBT LUWID('value') command, whichwas issued to purge indoubt information about thespecified luwid, completed successfully. The indoubtinformation was purged.value

The value specified for the LUWID keyword in the -RESET INDOUBT LUWID(value) command that isbeing processed.

System actionSystem processing continues normally.

DSNL446I COLD START WILL BE PERFORMEDWITH nettype netvalue

ExplanationA -RESET INDOUBT LUNAME('luname') FORCE or a -RESET INDOUBT IPADDR('ipaddr') FORCE commandissued to force a cold start completed successfully.The next connection with 'luname' or 'ipaddr' is a coldstart.nettype

Identifies the type of network used to access theremote site. There are two possible values:LU --





• If nettype is IPADDR, netvalue specifies the IPaddress of the remote location.


DSNL447I CANNOT DELETE ENTRY valueBECAUSE THERE IS AN INDOUBTTHREAD TO BE RESOLVED FIRST

ExplanationA -RESET INDOUBT command was issued withLUNAME(value), IPADDR(value), LOCATION(value), orLUWID(value). The value is an LU name, an IP address,a location, or a LUWID (or its token), that identifies alogical unit of work for which Db2 has participantindoubt resolution responsibility, coordinator indoubtresolution responsibility, or both.

System actionResynchronization responsibility information was notpurged. System processing continues normally.

User responseUse the information in this section to determine thecorrect action to take. Then issue the proper commandto perform that action.

The two most probable causes for the problem arethat the -RESET INDOUBT command was issued withthe wrong parameters, or that an incorrect 'value' wasspecified. Use the -DISPLAY THREAD(*)TYPE(INDOUBT) LOCATION(*) command to display theindoubt information known to Db2.

1. If the intent was to purge participant or coordinatorindoubt resolution responsibility, then examine the-DISPLAY THREAD output (DSNV401) to determinethe location name, or names, for which thisresponsibility is to be purged. Then use the -RESETINDOUBT LUNAME(luname) command with theFORCE option or the -RESET INDOUBT IPADDR(ip-address) command with the FORCE option to purgethis responsibility.

To determine the luname or IP address and resyncport for an upstream coordinator that can be usedwith the FORCE option, look at the coordinatorinformation after the DSNV406I message in the -DISPLAY THREAD output. There are two tokens


associated with the coordinator information thatare delimited by a dash (-) for SNA connections,and by a double period (..) for TCP/IP connections.

• The first token is the partner location name or"<luname>" for an SNA connection, or the IPaddress for the TCP/IP connection.

• The second token is the partner LU name for anSNA connection, or the resync port number for aTCP/IP connection.

To determine the luname or IP address and resyncport for downstream participants that can be usedwith the FORCE option, look at the location namesafter the V444 message and in the V450 messagein the DISPLAY THREAD output (DSNV401). Thereare two or three tokens associated with theparticipant location.

• The first token is the partner location name.• The second token is the partner LU name for an

SNA connection, or the IP address for a TCP/IPconnection. The second token is delimited fromthe first token by a dash (-).

• The third token is the partner resync port number.The third token appears only if the second tokenis an IP address, and is delimited from the secondtoken by a double period (..).

Remember that the FORCE option causes Db2 topurge all knowledge of indoubt resolutionresponsibility involving the LUNAME or IPADDRvalues specified in the command.

Use caution when using the FORCE parameter topurge participant indoubt information when noerrors are precluding automatic resolution.Normally, after the use of the RECOVER INDOUBTcommand, automatic resolution with thecoordinator determines if heuristic damageoccurred. This detection is lost if RESET INDOUBTis used before automatic resolution with thecoordinator can be achieved.

Use caution when using the FORCE parameter topurge coordinator indoubt information when noerrors are precluding automatic resolution. Oncethe information is purged, any participant that isindoubt is forced to use a heuristic decision processto resolve the indoubt logical unit of work.

2. Examine the -DISPLAY THREAD output. If the valuespecified in the command (and displayed in theDSNL447I message) is incorrect, determine thecorrect value and reissue the command using thecorrect value.

Related reference-RESET INDOUBT (Db2) (Db2 Commands)-RECOVER INDOUBT (Db2) (Db2 Commands)

-DISPLAY THREAD (Db2) (Db2 Commands)Related informationDSNV401IDISPLAY THREAD REPORT FOLLOWS -DSNL447ICANNOT DELETE ENTRY value BECAUSE THEREIS AN INDOUBT THREAD TO BE RESOLVEDFIRST

DSNL448I UNABLE TO FORCE COLD STARTWITH nettype netvalue, SESSIONSTILL EXISTS

ExplanationA -RESET INDOUBT LUNAME('luname') FORCE or a -RESET INDOUBT IPADDR('ipaddr') FORCE commandwas issued to force a cold start, but networkconnections still exist between Db2 and the partner'luname' or 'ipaddr'. The information related to thispartner was not purged, so a cold start is notperformed.nettype

Identifies the type of network used to access theremote site. There are two possible values:LU --





• If nettype is IPADDR, netvalue specifies the IPaddress of the remote location.


User responseFor SNA, you can use the VTAM command DISPLAYNET to determine the existence of sessions betweentwo logical units. Terminate the sessions by using theVTAM command VARY NET,TERM to allow the RESETINDOUBT to occur. For TCP/IP, terminate allconnections to the IP address.Determine the correctluname or ipaddr and reissue the command.

DSNL449I DB2 HAS NO INFORMATIONRELATED TO LUNAME luname


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_resetindoubt.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_recoverindoubt.html


ExplanationA -RESET INDOUBT LUNAME('luname') FORCEcommand was issued but Db2 has no knowledge ofthe specified 'luname'.luname

The logical unit name, as defined to VTAM, of thecoordinator or participant

System actionNo information was purged. System processingcontinues normally.

User responseDetermine the correct luname as follows:

• Use the -DISPLAY THREAD(*) TYPE(INDOUBT)LOCATION(*) command to determine locations forwhich Db2 has indoubt responsibility.

• Query the SYSIBM.LOCATIONS table to correlate alocation name with an luname. The LINKNAMEcolumn contains the luname associated with thelocation name in the LOCATION column.

Then reissue the command, specifying the correctluname.

DSNL450I DDF THREAD luwid=token ISBETWEEN PHASE 1 AND PHASE 2OF COMMIT. THREAD IS NOW ANINDOUBT THREAD AS A RESULTOF CANCEL REQUEST.

ExplanationThe identified DDF thread was in a prepared statewaiting for the commit or backout decision of thecommit coordinator. The thread cannot be canceled inthis state. However, the thread was removed from theactive state and placed into the indoubt state. Theconversation with the coordinator was deallocated.The thread is now indoubt and appears in the displaythread report for indoubt threads. The resources heldby the thread continue to be held. Automaticresolution of the indoubt state is attemptedperiodically. Resources held by the thread are releasedafter indoubt resolution occurs.luwid=token



Operator responseIf the purpose of canceling this thread was to free theresources held by the thread, call the databaseadministrator.

Database Administrator Action: To release theresources held by the indoubt thread before automaticresolution with the coordinator, a manual commit orabort decision can be made with the RECOVERINDOUBT command. First, issue the DISPLAY THREADcommand for an indoubt thread report, which includesthe subject thread. From this report, determine thename of the coordinator. Contact the coordinatorsystem and find out whether a commit or abortdecision was made.

DSNL451I QUALIFYING INDOUBTINFORMATION FOR LUNAMEluname NOT FOUND

ExplanationA -RESET INDOUBT LUNAME('luname') command wasissued, but Db2 has no indoubt information about thespecified luname.luname

The logical unit name, as defined to VTAM, of thecoordinator or participant


User responseUse the -DISPLAY THREAD(*) TYPE(INDOUBT)LOCATION(*) command to list the locations for whichDb2 has indoubt information. Entries associated with aparticular LUNAME have a location name in this form:'<luname>'. Use 'luname' (without the enclosingbrackets) as the input string to RECOVER INDOUBT.

After determining the correct luname, reissue thecommand.

DSNL452I QUALIFYING INDOUBTINFORMATION FOR LUNAMEluname HAS BEEN PURGED

ExplanationA -RESET INDOUBT LUNAME('luname') command,which was issued to purge indoubt information aboutthe specified luname completed successfully. Theindoubt information was purged.


lunameThe luname specified for the LUNAME keyword inthe -RESET INDOUBT LUNAME(luname) commandbeing processed.


DSNL453I csect QUALIFYING INDOUBTINFORMATION FOR IPADDRipaddr NOT FOUND

ExplanationA -RESET INDOUBT IPADDR('ipaddr') command wasissued, but Db2 has no indoubt information about thespecified IP address.csect

The CSECT name of the Db2 module that issuedthe message

ipaddrThe IP address of the coordinator or participant.


User responseUse the -DISPLAY THREAD(*) TYPE(INDOUBT)LOCATION(*) command to list the locations for whichDb2 has indoubt information. Entries associated withTCP/IP have a string with this format in the LOCATIONfield: "nnn.nnn.nnn.nnn".

After determining the correct ipaddr, reissue thecommand.

DSNL454I csect QUALIFYING INDOUBTINFORMATION FOR IP ADDRESSipaddr HAS BEEN PURGED

ExplanationA -RESET INDOUBT IPADDR('ipaddr') command,which was issued to purge indoubt information aboutthe specified IP address completed successfully. Theindoubt information was purged.csect

The CSECT name of the Db2 module that issuedthe message

ipaddrThe IP address specified for the IPADDR keywordin the -RESET INDOUBT IPADDR(ipaddr) commandbeing processed


DSNL455I csect DB2 HAS NO INFORMATIONRELATED TO IP ADDRESS ipaddr

ExplanationA -RESET INDOUBT IPADDR('ipaddr') FORCEcommand was issued but Db2 has no knowledge ofthe specified 'ipaddr'.csect

The CSECT name of the Db2 module that issuedthe message.

ipaddrThe IP address of the coordinator or participant.

System actionNo information was purged. System processingcontinues normally.

User responseDetermine the correct luname as follows:

• Use the -DISPLAY THREAD(*) TYPE(INDOUBT)LOCATION(*) command to determine locations forwhich Db2 has indoubt responsibility. Entriesassociated with TCP/IP locations specify"nnn.nnn.nnn.nnn" in the LOCATION field.

Reissue the command; specify the correct ipaddr.

DSNL500I CONVERSATION FAILED TOLOCATION=locnameRESOURCE=luname.modename.convid.sessid RTNCD=global vtamprimary return code FDBK2=globalvtam secondary return codeRCPRI=appc-specific primaryreturn code RCSEC=appc-specificsecondary return code SENSE=snasense code

ExplanationAn advanced program-to-program communications(APPC) conversation failed, or could not be allocated,because a VTAM return code indicates a conversationfailure. VTAM return codes are defined in z/OSCommunications Server SNA Programmer's LU 6.2Reference.

SNA sense codes that start with 00 represent Db2reason codes.


The variables that are not return codes are describedas follows:Variable

Descriptionlocname

The location name associated with the remote site.luname

The VTAM LU name associated with the remotelocation.

modenameThe logon mode used by Db2 to allocate theconversation.

convidThe conversation identifier given Db2 by VTAMwhen the conversation was allocated.

sessidThe session identifier given Db2 by VTAM when theconversation was allocated.

System actionCommunication on the conversation is discontinued.


System programmer responseTake the actions that are specified for the SNA sensecode and Db2 reason code values.

Related conceptsDb2 reason codes (Db2 Codes)Related referenceSNA sense codes (Db2 Codes)

DSNL501I CNOS PROCESSING FAILED FORLU luname AND MODE modenameRTNCD=global vtam return codeFDBK2=global vtam secondaryreturn code RCPRI=appc-specificprimary return code RCSEC=appc-specific secondary return codeSENSE=vtam sense code

ExplanationA failure occurred while attempting to negotiate limitswith the specified location for a LU and mode. VTAMreturn codes are described in z/OS CommunicationsServer SNA Programmer's LU 6.2 Reference. VTAMsense codes that start with 00 represent Db2 reasoncodes.

The variables are described as follows:

lunameThe VTAM LU name associated with the remotelocation.


System actionAll communication to the remote location fails until thelimits can be negotiated with the remote location.


System programmer responseRefer to z/OS Communications Server SNAProgrammer's LU 6.2 Reference and the Db2 reasoncode for failure analysis.


DSNL502I SYSTEM CONVERSATION FAILEDTO LOCATION locnameRESOURCE=luname.modename.convid.sessid RTNCD=global vtamprimary return code FDBK2=globalvtam secondary return codeRCPRI=appc-specific primaryreturn code RCSEC=appc-specificsecondary return code SENSE=snasense code

ExplanationA system conversation failed, or could not beallocated, because VTAM returned a nonzero returncode.

SNA sense codes that start with 00 represent Db2reason codes.

locnameThe location name associated with the remote site.

lunameThe VTAM LU name associated with the remotelocation.


convidThe conversation identifier given Db2 by VTAMwhen the conversation was allocated.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_snacodes.html


sessidThe session identifier given Db2 by VTAM when theconversation was allocated.

System actionCommunication on the conversation is not allowed.


System programmer responseTake the actions that are specified for the SNA sensecode and Db2 reason code values.

Related conceptsDb2 reason codes (Db2 Codes)Related referenceSNA sense codes (Db2 Codes)Related informationReturn Codes (z/OS Communications Server:SNA Programmer's LU 6.2 Guide)

DSNL504I csect-name RESOURCEUNAVAILABLE REASON=reasonTYPE=resouce-typeLOCATION=locationNAME=resource-name

ExplanationThe requested function requires a resource that iscurrently unavailable.


reasonThe reason that the resource is unavailable.

locationThe location of the unavailable resource.


Operator responseNote the reason, type codes, location, and name.


DSNL510I csect-name CONVLIMITNEGOTIATED FROM x TO y WITHLOCATION locname FOR LU lunameAND MODE modename

ExplanationThe maximum conversation limit is changed for amode with a remote subsystem. The limit mightchange when a CNOS request is received from or sentto a remote subsystem, and the limit is determined byVTAM.x

The most recent value of CONVLIMIT before thelast CNOS request was processed by advancedprogram-to-program communications (APPC)/VTAM for the specified mode name to the specifiedlocation.

yThe current value of CONVLIMIT for the specifiedmode name to the specified location.

locnameThe location name associated with the remote sitethat sent the CNOS request to the local Db2subsystem, or received the CNOS request from thelocal Db2 subsystem.

lunameThe VTAM LU name associated with the remotelocation that had its CONVLIMIT changed.

modenameThe logon mode for the specified location that hadits CONVLIMIT changed.

System actionConversation requests are queued when the maximumconversation limit is reached for a mode to remotesubsystem.

DSNL511I csect-name TCP/IPCONVERSATION FAILED TOLOCATION location-nameIPADDR=ip-address PORT=portSOCKET=socket RETURNCODE=return-code REASONCODE=reason-code

ExplanationA TCP/IP socket call failed with the error conditionidentified by the return code and reason code.




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_snacodes.html

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.istp620/oprcntl.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.istp620/oprcntl.htm


location-nameThe location name associated with the remote site.

ip-addressThe IP address of the remote site.

portThe TCP/IP port used by the remote site.

socketThe TCP/IP socket call that returned the error.

return-codeThe error condition reported by TCP/IP, as adecimal number. This code is issued by z/OS UNIXSystem Services or z/OS Communications Server.

A 3448 return code condition is typically related toa TCP/IP DROP-related event, such as the result ofa TCP/IP DROP command. Db2 also uses a TCP/IPDROP service for various cancel-related events,which might include the z/OS CANCEL command,the Db2 CANCEL THREAD command, or Db2 idle-thread timeout conditions.

reason-codeFurther detail associated with the TCP/IP returncode, as a hexadecimal number. This code isissued by z/OS UNIX System Services or z/OSCommunications Server.

The following values together indicate a zero-lengthreceive, which is considered a closed condition:

• SOCKET=RECV• RETURN CODE=0• REASON CODE=00000000

System actionCommunication on the conversation is discontinued.


System programmer responseUse the information provided in the message to correctthe problem.


Problem determinationDetermine the meaning of the return and reason codesissued by z/OS UNIX System Services or z/OSCommunications Server.

Related referencez/OS UNIX System Services: Messages andCodesz/OS Communications Server: IP and SNACodes

DSNL512I csect-name TCP/IP socket FAILEDWITH RETURN CODE=return-codeAND REASON CODE=reason-code

ExplanationA TCP/IP socket call used to establish communicationbetween Db2 and TCP/IP failed.


socketThe name of the TCP/IP socket call that failed.

return-codeThe return code reported by TCP/IP, as a decimalnumber. This code is issued by z/OS UNIX SystemServices or z/OS Communications Server.

reason-codeThe reason code reported by TCP/IP, as ahexadecimal number. This code is issued by z/OSUNIX System Services or z/OS CommunicationsServer.

System actionDb2 will periodically retry the socket call to establishTCP/IP communication.


System programmer responseThe response is based on the TCP/IP socket call thatfailed.

socket=GETHOSTNAMEsocket=GETNAMEINFO(ip-address)socket=GETADDRINFO(host-name)

The GetHostName, GetNameInfo, or GetAddrInfocall has failed.

During DDF initialization, Db2 first determines itshost name using a GetHostName socket call. Db2must then determine its IP address. If an IPaddress is specified in the BSDS using theDSNJU003 utility, or on the PORT statement in theTCP/IP profile, then Db2 uses this IP address.Otherwise, Db2 executes a GetAddrInfo(host-name) socket call, using the host-name that was


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxa800/abstract.html


http://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.cs3cod0/abstract.html


returned on the prior GetHostName socket call,which returns the first IP address listed in thename server or local host table.

Important: The host name or IP address returnedcould depend on the selected TCP/IP stack, in theevent that there are multiple TCP/IP stacks. Db2requires z/OS UNIX System Services sockets, andit is z/OS UNIX System Services that determinesthe TCP/IP stack to use. z/OS UNIX SystemServices provides a way for users to select aspecific TCP/IP stack by using the BPXTCAFFutility.

Db2 then issues a GetNameInfo socket call todetermine the domain name associated with thederived IP address.

The z/OS Resolver handles the GetNameInfosocket call because Db2 uses the z/OS UNIXSystem Services Asynchronous Sockets interface.This resolver uses the resolver configurationinformation available to DDF. Until this informationfor the selected TCP/IP is correctly specified forDDF, the z/OS Resolver will be unable to determinethe domain name for DDF. You can find the searchorder for the "resolver configuration files" for az/OS application, such as DDF, in the IPConfiguration manual for the appropriate level ofthe Communication Server for your z/OS operatingsystem.

socket=GETHOSTNAMEDb2 DDF initialization invoked a TCP/IPGetHostName socket call in order to determinethe host name associated to TCP/IP, and hencethe host name associated with the Db2subsystem. However, the call failed and Db2 isnot able to determine the host name. Db2retries the socket call periodically.

socket=GETNAMEINFO(ip-address)Db2 invoked a TCP/IP GetNameInfo socket callto determine the domain name for thespecified IP address. However, the call failedand Db2 is not able to determine the domainname. Db2 retries the socket call periodically.

socket=GETADDRINFO(host-name)Db2 invoked a TCP/IP GetAddrInfo socket callto determine the IP address associated withthe specified host name. However, the callfailed and Db2 is not able to determine the IPaddress. Db2 retries the socket callperiodically.

If you want a BSDS-specified IP address,correct the BSDS. This requires you to stop andrestart Db2. Otherwise, verify that the providedhost name is correct and take the appropriateaction:

• If the host name is incorrect, correct the hostname in the appropriate resolverconfiguration file, refresh TCP/IP, and thenstop and start DDF so that the new hostname is refreshed for DDF initialization.

• If the host name is correct, then TCP/IP isunable to resolve the host name to an IPaddress. You must make changes in order toallow for proper host name to IP addressresolution. If the changes have been made tothe name server or local host table, refreshthe resolver.

socket=POLLThe online ZPARM was changed using the SETSYSPARM command, changing the MAXDBAT froma positive value to zero. In this case, the messageis informational, indicating that Db2 terminated itsTCP/IP listening capability for SQL related workbecause Db2 can no longer accept SQL relatedconnections from remote partners when MAXDBATis set to zero.

socket=SHUTDOWN_REG (USS_UNAVAILABLE)The z/OS UNIX System Services (USS/OMVS)environment is not available. DDF start processingcontinues and this message is periodicallyrepeated until the Unix System Servicesenvironment becomes available or DDF is stopped.You can use the z/OS "F OMVS, RESTART"command to start the z/OS UNIX System Servicesenvironment.

socket=SETRLIMITWhen reason code=1148033C, DDF needs to bedefined as a superuser. For instructions on how toenable DDF as a superuser, see Enabling DDF forUNIX System Services and TCP/IP (Db2Installation and Migration).

socket=TCPKEEPALIVEDb2 issues this socket call as a result of the TCP/IPKeepAlive value specified in the Db2 parametersmodule (usually DSNZPARM). You may specify thisvalue by the TCP/IP KEEPALIVE value in theDSNTIP5 installation panel. Another way to specifythe value is through the TCPKPALV value in theDSN6FAC macro, used to build the Db2parameters module.

In this situation, processing continues, and Db2does not retry the socket call. Verify that theTCP/IP stack being used by Db2 contains therequired companion support for this function. Ifnot, modify the Db2 parameter module to preventDb2 from attempting to override the TCP/IP stackvalue.

socket=BSDS_ERROR (ADDRESS_ON_PORT_STMT)An IP address is specified in both the BSDS andthe PORT statement of the TCP/ IP profile. An


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_enableddf4uss.html



address should be specified in only one place. Thatis, Db2 detected that IP addresses have beenspecified in the BSDS (through the IPV4, GRPIPV4,IPV6, and GRPIPV6 keywords of the DSNJU003Change Log Inventory utility) and also in theTCP/IP profile on the PORT statement for the portvalue to be used by this subsystem. Only one of thespecifications can now have IP addresses. The Db2TCP/IP environment will not initialize, and the erroris periodically repeated until the error is corrected.

One of the IP address specifications must beremoved from the BSDS or from the TCP/IP profile.However, the BSDS specification should beretained because the recommendation is to useBSDS specifications to define the IP addressesthat are to be associated to Db2, and, becauseremoving the BSDS specifications would requireDb2 to be stopped. In this case, to allow theinitialization of the Db2 TCP/IP environment tocontinue. The TCP/IP profile PORT statement canbe changed to remove the IP addresses and thenthe changed specifications can be dynamicallybrought on-line, which favors the BSDSspecifications.

socket=BSDS_ERROR(IPv6_REQUIRES_DUALMODE_STACK)

A member or subsystem, or possibly a group, IPv6address is specified in the BSDS without TCP/IPdual mode stack enabled. Db2 ignores all IPv6addresses defined in the BSDS and DDF start-processing continues normally.

You should either enable a dual mode stack ordelete all of the BSDS-defined IPv6 addresses anduse only IPv4 addresses.

socket=BINDSPECIFIC NOT SUPPORT WITHSECURE PORT

A secure port was specified in the BSDS but an IPaddress is simultaneously defined on the PORTstatement in the TCP/IP profile (PROFILE.TCPIP).

DDF supports secure ports only when it is listeningon the INADDR_ANY.

socket=DVIPA ACTIVATION(ip-address)The specified IP address cannot be activated as aVIPARANGE DVIPA. Db2 does not know whetherthe specified IP address was intended to be usedas a DVIPA. If it was intended to be used as aDVIPA, correct the error and recycle DDF toactivate it. However, if the IP address was notintended to be used as a DVIPA, ignore thismessage.

socket=EZBNMIF4_DROPCONDb2 invoked the TCP/IP EZBNMIF4 (EZBNMIFR)service to drop a connection. The call failed butDb2 processing continues. Db2 periodically issues

the message until the error is corrected. Refer toUsing the EZBNMIFR requests (z/OSCommunications Server: IP Programmer's Guideand Reference) for an explanation of the return andreason code values.

The most common cause for the failure is a returncode value of 111 (EACCES) and a reason codevalue of 77E800DC (JRSAFNotAuthorized). Thisreturn and reason code indicates that TCP/IPdetermined that RACF security profiles were notdefined to permit Db2 to use the service. The userID that is associated with the ssnmDIST startedtask requires CONTROL access to theMVS.VARY.TCPIP.DROP command for theOPERCMDS class. Refer to Enabling DDF for UNIXSystem Services and TCP/IP (Db2 Installation andMigration) for more information.

socket=ACCEPT(ip-address..0)When return-code=3448 and reason-code=768F0442, TCP/IP DVIPA services are nolonger available. TCP/IP deleted the IP address,and that IP address is no longer usable. TheTCP/IP listener is disabled.

The Db2 TCP/IP listener attempts to restart every30 seconds. When TCP/IP DVIPA services arerestored, the TCP/IP listener restarts and issuesmessage DSNL519I or DSNl523I to indicate thatTCP/IP DVIPA services are restored.

socket=BIND(ip-address..0)When return-code=1116 and reason-code=744C7230, the IP address that is defined inthe BSDS is not valid or not usable. The Db2TCP/IP listener is not available, but DDF startupcompletes.

To correct this error, follow these steps:

1. Stop Db2.2. Run the change log inventory utility

(DSNJU003) DDF statement to set a valid andusable IP address in the BSDS.

3. Restart Db2.

When return-code=1116 and reason-code=744C7231, there are no available ports inthe TCP ephemeral port range that can be used byDb2 to determine the availability of DVIPAservices.

The Db2 TCP/IP listener continues its setup butDb2 cannot determine the availability of DVIPAservices.

To correct this error, increase the range of TCPephemeral ports on the TCPCONFIGEPHEMERALPORTS definition in the TCP/IP profileconfiguration. Refer to TCPCONFIG statement


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.halx001/requestnm.htm






http://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.halz001/tcpconfigstatement.htm

(z/OS Communications Server: IP ConfigurationReference) for more information on theTCPCONFIG TCP/IP profile configurationstatement.

When return-code=111 and reason-code=744C735A, Db2 does not have authority toaccess an unreserved TCP protocol port that canbe used by Db2 to determine the availability ofDVIPA services.


To correct this error, create a PORT UNRSV TCPdefinition that allows Db2 to access unreservedports in the TCP/IP profile configuration. Refer toPORT statement (z/OS Communications Server: IPConfiguration Reference) for more information onthe PORT statement.

When return-code=111 and reason-code=744C735B, Db2 does not have permissionfrom the System authorization facility (SAF) toaccess an unreserved TCP protocol port that canbe used by Db2 to determine the availability ofDVIPA services.


To correct this error, grant to the Db2 user ID READpermission to RACF resourceEZB.PORTACCESS.sysname.tcpname.safname. Theparts of the resource name are:

• EZB.PORTACCESS is constant• sysname is the value of the MVS &SYSNAME.

system symbol.• tcpname is the name of the procedure used to

start the TCP stack.• safname is the value of the SAF keyword in the

PORT UNRSV TCP command.

Refer to PORT statement (z/OS CommunicationsServer: IP Configuration Reference) for moreinformation on the PORT UNRSV TCP statement.

socket=LISTEN(ip-address..0)

When return-code=111 and reason-code=744C735A, Db2 does not have authority toaccess an unreserved TCP protocol port that canbe used by Db2 to determine the availability ofDVIPA services.


To correct this error, create a PORT UNRSV TCPdefinition that allows Db2 to access unreservedports in the TCP/IP profile configuration. Refer toPORT statement (z/OS Communications Server: IPConfiguration Reference) for more information onthe PORT statement.

When return-code=111 and reason-code=744C735B, Db2 does not have permissionfrom the System authorization facility (SAF) toaccess an unreserved TCP protocol port that canbe used by Db2 to determine the availability ofDVIPA services.


To correct this error, grant to the Db2 user ID READpermission to RACF resourceEZB.PORTACCESS.sysname.tcpname.safname. Theparts of the resource name are:

• EZB.PORTACCESS is constant• sysname is the value of the MVS &SYSNAME.

system symbol.• tcpname is the name of the procedure used to

start the TCP stack.• safname is the value of the SAF keyword in the

PORT UNRSV TCP command.

Refer to PORT statement (z/OS CommunicationsServer: IP Configuration Reference) for moreinformation on the PORT UNRSV TCP statement.



If socket=BINDSPECIFIC NOT SUPPORT WITHSECURE PORT, check whether the PTF for APARPI92982 was applied. If not, apply that PTF.

Related conceptsUpdate the BSDS with the DSNJU003 utility(Db2 Data Sharing Planning and Administration)Related tasksRequesting transport affinity (BPXTCAFFinformation) (z/OS UNIX System ServicesPlanning)Enabling DDF for UNIX System Services andTCP/IP (Db2 Installation and Migration)




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.halz001/portstatement.htm










http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxb200/tranreq.htm





Related referencez/OS UNIX System Services: Messages andCodesz/OS Communications Server: IP and SNACodesDSNJU003 (change log inventory) (Db2 Utilities)PORT statement (z/OS Communications Server:IP Configuration Reference)TCPCONFIG statement (z/OS CommunicationsServer: IP Configuration Reference)Related informationDSNL519Icsect-name TCP/IP SERVICES AVAILABLE FORDOMAIN domain AND PORT tcpportDSNL523Icsect-name TCP/IP SERVICES AVAILABLE FORIP ADDRESS ipaddr AND PORT port

DSNL513I csect TCP/IP GETHOSTBYNAMEFAILED WITH ERRNO=errno FORDOMAIN domain

ExplanationDb2 encountered a TCP/IP gethostbyname socket callerror when attempting to convert a TCP/IP domainname into an IP address.Variable

Descriptioncsect


errnoThe error condition reported by TCP/IP.

domainThe TCP/IP domain name that Db2 wants toconvert into an IP address. Db2 obtains thedomain value from the IPADDR column of theSYSIBM.IPNAMES communications database tableor from the trusted context ADDRESS attributedefined in the SYSIBM.SYSCTXTTRUSTATTRScatalog table.

System actionIf the row in SYSIBM.IPNAMES containing thespecified domain in the IPADDR column is invalid, then

• If the error occurs during DDF startup, the row inSYSIBM.IPNAMES is ignored.

• If the error occurs during an SQL statement, the SQLstatement fails and the location associated with theSYSIBM.IPNAMES row is not available for TCP/IPcommunication.

If the trusted context ADDRESS attribute containingthe specified domain defined in theSYSIBM.SYSCTXTTRUSTATTRS is invalid, then

• If the error occurs during implicit trusted connectionprocessing, then the error is ignored and theconnection is established without any additionalprivileges.

• If the error occurs during explicit trusted connectionprocessing, then the connection processing fails.


System programmer responseCorrect the IPADDR column value in SYSIBM.IPNAMESor register the domain with TCP/IP. Correct the trustedcontext ADDRESS attribute value using the SQL ALTERTRUSTED CONTEXT statement. register the domainwith TCP/IP.


Problem determinationSee System Programmer Response.

Related referenceIPNAMES catalog table (Db2 SQL)Related informationSocket return codes (ERRNOs) (z/OSCommunications Server: IP and SNA Codes)

DSNL514I csect-name TCP/IP SERVICE servIS NOT DEFINED

ExplanationThe TCP/IP getservbyname socket call did not find amatching definition for serv.Variable

Descriptionserv

The TCP/IP service name that Db2 wants toconvert into a TCP/IP port number. Db2 obtains theservice name from the PORT column of theSYSIBM.LOCATIONS communication databasetable.

System actionThe row in SYSIBM.LOCATIONS containing thespecified service name in the PORT column is invalid.











https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmipnamestable.html

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.cs3cod0/syserret.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.cs3cod0/syserret.htm

The associated LOCATION cannot be used for TCP/IPcommunication. If the error occurs during an SQLstatement, the SQL statement fails.


System programmer responseIf the value specified by serv is incorrect, correct thePORT column value in SYSIBM.LOCATIONS.

If the value specified by serv is correct, register theservice name with TCP/IP.

TCP/IP service names are case sensitive, so make surethat the PORT column in SYSIBM.LOCATIONS is anexact match for the service name defined to TCP/IP.


Problem determinationSee System Programmer Response.

DSNL515I csect-name TCP/IP BIND FAILEDFOR PORT port WITH RETURNCODE=return-code AND REASONCODE=reason-code

ExplanationDb2 encountered an error on the TCP/IP bind socketcall while attempting to register a TCP/IP port numberwith the TCP/IP instance.


portThe TCP/IP port number that Db2 was unable toregister with the TCP/IP instance.

return-codeThe return code reported by TCP/IP, as a decimalnumber. This code is issued by z/OS UNIX SystemServices or z/OS Communications Server.

reason-codeThe reason code reported by TCP/IP, as ahexadecimal number. This code is issued by z/OSUNIX System Services or z/OS CommunicationsServer.

System actionThe request fails. Db2 will continue to try to activatethe TCP/IP port number periodically.


System programmer responseIf this error occurs for the TCP/IP port that is used forincoming DRDA requests, the error is probably causedby Db2 restarting on a CEC that already has anotherDb2 subsystem using the DRDA port number.

If this error occurs for a TCP/IP port that is used forincoming DRDA requests to an ALIAS, the error isprobably caused by some of the reasons that an errorwould occur for the normal DRDA request port. Checkto ensure that the port value was also not previouslyreserved for another application in the system'sTCP/IP profile.

Define the TCP/IP port number used by Db2 to theTCP/IP instance, or use the change log inventory utilityto correct the TCP/IP port number used by Db2.



Related referencez/OS UNIX System Services: Messages andCodesz/OS Communications Server: IP and SNACodes

DSNL516I csect-name LANGUAGEENVIRONMENT SERVICES NOTAVAILABLE. CEEPIPI ROUTINECANNOT BE LOADED

ExplanationDb2 must load the Language Environment interfacemodule (CEEPIPI) to process functions requiringLanguage Environment services. These LanguageEnvironment services are required for TCP/IP socketcalls, encryption and decryption, and so on. If theCEEPIPI module is not included in an accessible dataset such as STEPLIB data sets or the LPA library, DDFis unable to use the Language Environment.

System actionDDF startup continues, but DDF users cannot use Db2functions that require Language Environment services.






System programmer responseAdd the Language Environment library to the DDFSTEPLIB concatenation or to the LPA library. TheLanguage Environment library must be APF authorizedwhen it appears in the DDF STEPLIB concatenation.

Problem determinationCollect the following diagnostic item listed in


.

DSNL517I csect-name CEEPIPI func SERVICEFAILED WITH RETURNCODE=return-code

ExplanationDb2 uses the Language Environment CEEPIPI serviceto issue certain TCP/IP socket calls. The LanguageEnvironment return code return-code was notexpected for the indicated Language Environmentfunction call.func

The function requested by Db2. Possible valuesare:add_entry(module-name)

Add an entry to the Language EnvironmentPIPI table dynamically. Module-name is thename of the module that failed to be added tothe PIPI table.

call_subRun a program that issues a TCP/IP socket callusing an existing Language Environment runtime environment.

del_subDelete an entry from the LanguageEnvironment PIPI table dynamically.

init_subCreate Language Environment sub run timeenvironment.

termTerminate the Language Environment run timeenvironment.

return-codeThe return code received from CEEPIPI.

System actionThe attempt to issue the Language Environmentrequest fails.

If this message is issued during DDF startup, DDFstartup continues.

If this message is issued during an SQL statement, a-904 SQLCODE is returned to the calling application.

System programmer responseSee Problem Determination.



If the function requested by Db2 was add-entry(module-name), an incorrect link edit of themodule could create unresolved references. Todetermine if link edit problems exist, run the z/OSAMBLIST utility with LISTLOAD and OUTPUT=XREF.

Related referencez/OS Communications Server: IP and SNACodesRelated information-904 (Db2 Codes)

DSNL518I csect-name LE/370 ENCLAVEFAILED WITH RETURN CODE=ercAND FEEDBACK=fi

ExplanationDb2 uses the Language Environment CEEPIPI call_subservice to execute certain TCP/IP socket calls. TheCEEPIPI interface returned information indicating afailure occurred while executing the TCP/IP socket.erc

The Language Environment enclave return code.fi

Contains one or two message identifiers. Themessage identifiers are constructed from theLanguage Environment condition token.

The message identifiers are constructed asfollows:

• Single message: Facility_Id combined withMsg_No

• Two messages: Facility_Id combined withClass_Code and Facility_Id combined withCause_Code

System actionThe SQL statement fails with SQLCODE -904.





System programmer responseA description of the Language Environment enclavereturn code and the condition token are documentedin z/OS Language Environment Programming Guide.



• SYSABEND, SYSUDUMP, or SYSMDUMP output.

.

DSNL519I csect-name TCP/IP SERVICESAVAILABLE FOR DOMAIN domainAND PORT tcpport

ExplanationDb2 is ready to accept connections on any IP addresssupported by the TCP/IP stack. This message is issuedwhen re-initialization is successful. Db2 will not acceptany connection request until this message is issued.


domainThe TCP/IP domain name used by this Db2subsystem to accept incoming connectionrequests.

tcpportThe TCP/IP port number used by this Db2subsystem to accept incoming connectionrequests.

System actionThe Db2 TCP/IP port number is available to acceptincoming connection requests on any IP addresssupported by the TCP/IP stack.

Related conceptsTCP/IP access methods (Db2 Data SharingPlanning and Administration)

DSNL520I csect TCP/IP SERVICESAVAILABLE FOR RESPORT port

ExplanationDb2 encountered a TCP/IP failure during DDF startupprocessing. The DSNL515I message identifies thecause of the failure. After the failure is detected, DDFperiodically attempts to reinitialize TCP/IP to allow

TCP/IP resynchronization to occur. This message isissued when reinitialization is successful.Variable

Descriptioncsect


portThe TCP/IP port number used by this Db2subsystem to accept incoming resynchronizationconnection requests.

System actionThe Db2 TCP/IP port is available to accept incomingresynchronization connection requests.

DSNL521I csect-name INVALID DDF BSDSVALUES DETECTED(PORT=port,RESPORT=rportSECPORT=sport).

ExplanationDb2 encountered invalid values for the TCP/IP portnumbers in the DDF record of the BSDS. Valid TCP/IPport numbers must obey the following rules:

• If PORT or SECPORT is non-zero, RESPORT mustalso be non-zero.

• If RESPORT is non-zero, PORT or SECPORT mustalso be non-zero.

• PORT, RESPORT, and SECPORT must not specify thesame value.

VariableDescription

portThe TCP/IP port number used by this Db2subsystem to accept incoming DRDA SQLconnection requests.

rportThe TCP/IP port number used by this Db2subsystem to accept incoming two-phase commitresynchronization requests.

sportThe TCP/IP port number used by this Db2subsystem to accept incoming secure DRDAconnection requests.

System actionDDF startup terminates abnormally.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/dshare/src/tpc/db2z_tcpipaccessmethods.html


System programmer responseUse the Change Log Inventory utility (DSNJU003) tocorrect the TCP/IP port numbers used by Db2.

DSNL523I csect-name TCP/IP SERVICESAVAILABLE FOR IP ADDRESSipaddr AND PORT port

ExplanationDb2 is ready to accept connections on the specified IPaddress and port.


ipaddrThe IP address used by this Db2 subsystem toaccept incoming connection requests.

portThe port number used by this Db2 subsystem toaccept incoming connection requests. It can be agroup SQL port, a resync port or an alias port.

System actionDDF is available to accept incoming requests on thespecified IP address and port. If the IP address isspecified on the PORT statement of the TCPIP profile,Db2 accepts connections only on the specified IPaddress. If the IP address is specified by either theDSNJU003 utility or the MODIFY DDF command, Db2accepts connections on any IP address active on thestack, including the specified IP address, regardless ofwhether a domain name is provided or not.

This message is issued each time that the listener isre-initialized to accept requests for the specified IPaddress and port.

System programmer responseIf you want Db2 to accept connections on any IPaddress, including the specified IP address, then theIP address must be specified in the BSDS. Specifying adomain name is optional when the IP address isspecified in the BSDS.

Related conceptsTCP/IP access methods (Db2 Data SharingPlanning and Administration)Related referenceDSNJU003 (change log inventory) (Db2 Utilities)-MODIFY DDF (Db2) (Db2 Commands)

DSNL600I RESOURCE UNAVAILABLECORRELATION ID=correlation-idCONNECTION ID=connection-id

LUW ID=luw-id=tokenREASON=reason-codeTYPE=resource-typeLOCATION=location-nameNAME=resource-name

ExplanationThis message is produced at the requesting site whena distributed request requires a resource that is notavailable.

correlation-idThe correlation identifier of the thread associatedwith the requester of the resource. Correlation IDsbeginning with '0nn' where nn is a number 01 - 28,identify system agents.

connection-idThe connection identifier of the requester.

luw-id=tokenThe logical unit of work ID of the thread followedby an '=' sign and a token which may be used inplace of luw-id in any Db2 command that acceptsluw-id as input.


location-nameThe location of the unavailable resource.


User responseSee Problem Determination.

Problem determinationThe reason the resource is unavailable is identified bythe reason code. Collect the information described forthe reason code received.



Related conceptsDb2 reason codes (Db2 Codes)Related informationDSNT500I







csect-name RESOURCE UNAVAILABLE REASONreason-code TYPE resource-type NAMEresource-name

DSNL601I command RESTSVC REPORTFOLLOWS -

ExplanationThis message displays output from the DISPLAY,START, or STOP RESTSVC command. The output for aDISPLAY RESTSVC command provides statusinformation of the REST services, which matched theone or more service name parameters. The output fora START or STOP RESTSVC command provides thestatus of processing the command against eachservice name parameter.

commandThe kind of RESTSVC command being performed:DISPLAY, START, or STOP

The remaining output consists of one or more of thefollowing messages in no particular order:

• DSNL602I: Invalid service name specified• DSNL603I: No services found• DSNL604I: Insufficient authority for command• DSNL605I: Services display limit reached• DSNL606I: All services not the only parameter• DSNL607I: Successful services status change• DSNL608I: Unsuccessful services status change• DSNL609I: Insufficient message space• DSNL610I: Display of services for a collection• DSNL615I: Display service continuation• DSN9022I: Successful command completion• DSN9023I: Abnormal command completion

Refer to the particular message for details on itsdisplay.



DSNL602I INVALID SERVICE NAMESPECIFIED – service_parm

ExplanationA specified service name parameter was not valid.

service_parmThe RESTSVC keyword parameter beingprocessed.

System actionProcessing of the command is terminated

User responseCorrect the service name parameter and reissue thecommand.

Problem determinationExamine the service_parm displayed. It must conformto the syntax of the RESTSVC keyword of the DISPLAY,START, or STOP RESTSVC command.

If the service_parm displayed appears to follow thecommand syntax, each service name parameter mustbe separated from each other by a comma(,). A commacannot be part of a parameter. One way that a commacould have become part of a service name parameteris that the entire parameter of the RESTSVC keywordwas delimited by apostrophes (’). Apostrophes shouldonly delimit a particular service name parameter if thecase of the service name parameter is to be preserved.Otherwise the service name parameter will be foldedto upper case prior to processing by Db2. For example,the RESTSVC specification RESTSVC('A.b,b.*')isincorrect, while the RESTSVC specificationRESTSVC('A.b','b.*') is correct.

Another possible issue is how the wildcard character,asterisk (*) is used. An asterisk can be used in twoways. An asterisk can be used when requesting todisplay all services (*.*) or when requesting to display asubset of services in a particular collection. Whendisplaying a subset of services, an asterisk can beused as a partial name of the service portion of aqualified/unqualified REST service name and can onlybe used as the last character of the partial name. Itcannot be used anywhere in the collection ID or theversion ID of a REST service name.

DSNL603I NO SERVICES FOUND FORservice_parm

ExplanationNo REST services were found to match a parameter ofthe RESTSVC keyword.



System actionProcessing of the command will be continued ifadditional service name parameters were provided.

User responseCorrect the service name parameter and reissue thecommand.

Problem determinationExamine the service_parm displayed. If the text isshown in upper case, and a service name parameterwith lower case characters was provided, the servicename parameter must be delimited by apostrophes (‘)to preserve the case.

DSNL604I USER HAS INSUFFICIENTAUTHORITY FOR commandRESTSVC OF service_parm

ExplanationThe invoker of the command does not have anecessary authority to process a RESTSVC commandagainst a provided RESTSVC keyword parameter.

command

The kind of RESTSVC command being performed:DISPLAY, START, or STOP.

service_parm

The RESTSVC keyword parameter beingprocessed.

System actionProcessing of the command will be continued, ifadditional service name parameters were provided.

User responseThe invoker of the RESTSVC command must have oneof the authorities outlined in the description of theparticular RESTSVC command. Obtain the necessaryauthority and reissue the command.

DSNL605I DISPLAY RESTSVC TERMINATEDWITH MAXIMUM SERVICES

ExplanationWhile processing a DISPLAY RESTSVC command, thelimit of the number of services which can be displayedby the command was reached.

System actionProcessing of the DISPLAY RESTSVC command isterminated.

User responseThe LIMIT keyword, of the DISPLAY RESTSVCcommand, provides a capability where the commandissuer can request the maximum number of RESTservices to be displayed. If not specified, the LIMITvalue defaults to 100. If the output from the commandexceeds the specified or defaulted limit, the commandwill terminate with this message. If it is not known howmany services could be displayed, then specifyLIMIT(*) on the command. Reissue the command witha LIMIT keyword that will permit all requested servicesto be displayed.

DSNL606I *.* MUST BE THE ONLY RESTSVCPARAMETER

ExplanationThe syntax rules of the RESTSVC command have beenviolated. An attempt to process the command againstall services (*.*) can only be requested by itself. Noother service name parameter can be provided.

System actionProcessing of the particular RESTSVC command isterminated.

User responseCorrect the RESTSVC keyword of the command byeither specifying the all services parameter (*.*) byitself or removing the all services parameter (*.*) whenspecific service name parameters are processed.Resubmit the command.

DSNL607I ALL SERVICES HAVE BEEN statusFOR service_parm

ExplanationA START or STOP RESTSVC command has successfullychanged the status of one or more REST services. Thestatus of the services that matched the service_parmhave been changed successfully.

statusThe new status of the changed REST services:STARTED or STOPREJ.



System actionThe changes to the status of the services arecommitted. Processing continues normally.


DSNL608I command RESTSVC OFservice_parm HAS FAILED DUE TOreason

ExplanationAn error was detected within Db2 while processing theservice name parameter.

commandThe kind of RESTSVC command being performed:DISPLAY, START, or STOP.


The reason for the failure can have the followingformats:

reason=REST SERVICES ENVIRONMENT NOTAVAILABLE

The REST services database objects either do notexist or are defined incorrectly.

reason= REASON CODE Db2_reason_codeDuring the processing of the command against theset of services identified by service_parm, a Db2failure occurred. That failure is represented byDb2_reason_code. In some cases, a Db2 messagemay have been issued on the console.

System actionThe command is terminated.

System programmer responseIf the reason for the failure is due to the REST servicesdatabase objects are not defined or are definedincorrectly, then create them using therecommendations found in Enabling Db2 RESTservices (Db2 REST services).

Otherwise, determine the meaning of theDb2_reason_code as it relates to table modificationsbeing performed against SYSIBM.DSNSERVICE.

If the reported DB2_reason_code is 00C900C0, a locktimeout was detected. The command could be retriedat a later time. However, holding the lock resourcesneeded for REST services database objects for anextended period of time is not normal.

It is possible Db2 messages may also have beendisplayed on the console. Review those messages foradditional information that may address how tocorrect the error.


DSNL609I DISPLAY TERMINATED DUE TOINSUFFICIENT MESSAGE SPACE

ExplanationThe DISPLAY RESTSVC command could not obtainstorage for additional messages. This situation onlyoccurs for long display requests, such as one thatrequests all services that have been defined.

System actionThe display is truncated.

User responseReissue the DISPLAY RESTSVC command and specifya smaller number of services. For example, specify apartial servicename in the DISPLAY RESTSVCcommand rather than the default (*.*).

DSNL610I

ExplanationThe message starts the output from the DISPLAYRESTSVC command for a qualified collection and itsone or more services. Multiple groupings of messagesbeginning with DSNL610I are possible from a singleDISPLAY RESTSVC command.

DSNL610I----COLLECTION=collidSERVICE VERSION STATUS service_name version statusservice_name version status DSNL610I----COLLECTION=collidSERVICE VERSION STATUS service_name version statusservice_name version status

The output that is displayed varies depending on thequalified collections and their qualified services. Thefollowing information can be provided in the output:

COLLECTION=collidThe collection id for the Db2 REST services that areincluded in the output. The collection id and the


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/restserv/src/tpc/db2z_createdbobjects4restserv.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/restserv/src/tpc/db2z_createdbobjects4restserv.html

lines that follow make up one grouping ofmessages that are output from the DISPLAYRESTSVC command. Each collection id groupingstarts with DSNL610I being displayed. Up to 3lines of output may be required to display a fullcollection id of 128 characters.

SERVICE service_name

The name of the service. Up to 3 lines of outputmay be required to display a full service name of128 characters.

VERSION versionThe version of the service. Up to 4 lines of outputmay be required to display a full version of 64characters. Version values can only be displayed ifDb2 REST services have been created since Db2REST service versioning was activated.

STATUS statusThe status of the service. The status can be any ofthe following values:STARTED

The service can be invoked.STOPREJ

The service was placed in this state by theSTOP RESTSVC command with theACTION(REJECT) option (which is the default).All invoke requests for the service are rejected.

STARTED*The service can be invoked and is the defaultversion of the service.

STOPREJ*The service was placed in this state by theSTOP RESTSVC command with theACTION(REJECT) option (which is the default).All invoke requests for the service are rejected.The service is also the default version of theservice.

If the service is in any of the stopped states, youcan use the START RESTSVC command to start theservice.

System actionThe DISPLAY RESTSVC command processingcontinues.


DSNL615I DISPLAY RESTSVC REPORTCONTINUE

ExplanationWhile processing a DISPLAY RESTSVC commandrequested from an MVS console, the console multipleline limit was about to be reached. The display of theset of services for a collection is temporarily halted.Once DSNL615I is issued, the display of the remainingservices of the halted collection is resumed. Thedisplay is resumed as if the collection id was initiallybeing displayed followed by its service names.

System actionProcessing of the DISPLAY RESTSVC continues.


DSNL700I csect-name CDB RESOURCEUNAVAILABLE, DEFAULTS MAY BEUSED REASON=reason TYPE=typeNAME=name

ExplanationThis message indicates that a requested functionrequired the CDB which is currently unavailable.Defaults can be used to allocate conversations or setconversation limits with VTAM and TCP/IP partners.

System actionIf the SYSIBM.MODESELECT table is unavailable,VTAM defaults are used to allocate conversations. Ifthe SYSIBM.LUMODES table is unavailable, VTAMdefaults can be used for conversation limits. If theSYSIBM.LOCATIONS, SYSIBM.IPNAMES,SYSIBM.LULIST, or SYSIBM.LUNAMES tables areunavailable, conversations can not be allocated toremote LOCATIONs.


Operator responseNote the REASON code, the TYPE code, and the NAME.See Problem Determination section for an explanationof the collected data.

Problem determinationThe reason the resource is unavailable is identified bya reason code. Use the table defined for messageDSNT500I to find the TYPE of resource identified inthe message.


Related conceptsSQL codes (Db2 Codes)Communications database for the requester(Managing Security)Communications database for the server(Managing Security)Related informationDSNT500Icsect-name RESOURCE UNAVAILABLE REASONreason-code TYPE resource-type NAMEresource-nameRecovering from communications databasefailure (Db2 Administration Guide)

DSNL701I CDB OBJECT object-name DOESNOT EXIST

ExplanationThe communications database (CDB) does not containobject-name. The incorrect object-name can be thedatabase name, the table space name, or the tablename.



System programmer responseDetermine what caused the failure, define the objectas required, and issue the -START DDF command.

Problem determinationPrint the definition of the communications database(CDB).

DSNL702I CDB TABLE table-name DOES NOTHAVE PROPER COLUMNDEFINITIONS, COLUMN column-name IS MISSING ORINCORRECTLY DEFINED

ExplanationThe communications database (CDB) needs adefinition for 'column-name' in 'tablename'. Thecurrent definition is missing or incorrect.



System programmer responseDetermine what caused the failure, define the columnas required, and issue the -START DDF command.


DSNL703I CDB TABLE table-name DOES NOTHAVE PROPER INDEXDEFINITIONS, INDEX index-nameIS MISSING OR INCORRECTLYDEFINED

ExplanationThe communications database (CDB) requires an indexname for table-name. The current definition is missingor incorrect.

System actionThe distributed data facility (DDF) terminates.


System programmer responseDefine the index as required and issue the -START DDFcommand.


Related tasksPopulating the communications database (Db2Installation and Migration)Related reference-START DDF (Db2) (Db2 Commands)Related informationRecovering from a problem with acommunications database that is incorrectlydefined (Db2 Administration Guide)



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_cdb4requester.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_cdb4requester.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_cdb4server.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_cdb4server.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recovercdbfailure.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recovercdbfailure.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_populatecdb.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recovercdbnotdefined.html



DSNL704I CDB OBJECT object-name DOESNOT HAVE PROPER REFERENTIALCONSTRAINT DEFINITIONS

ExplanationThe communications database (CDB) requiresreferential constraint definitions for object-name. Thecurrent definition is missing or incorrect.



System programmer responseDetermine what caused the failure, define the missingreferential constraint, and issue the -START DDFcommand.


Related conceptsThe role of the communications database (CDB)(Db2 Installation and Migration)Related tasksPopulating the communications database (Db2Installation and Migration)Populating the communications database foruse with TCP/IP (Db2 Installation andMigration)Related reference-START DDF (Db2) (Db2 Commands)

DSNL705I CDB IS UNAVAILABLE ORINCORRECTLY DEFINED

ExplanationDuring start-up of the distributed data facility, therequired CDB was unavailable or incorrectly defined.

System actionTermination of the DDF is initiated.


System programmer responseRefer to the previous message that specifies the causeof the CDB failure (DSNL700I, DSNL701, DSNL702I,DSNL703I, or DSNL704I). Determine what caused thefailure, fix the error condition, and issue the -STARTDDF command.



.

DSNL706I csect-name AN ERROR HASOCCURRED IN DDF EXIT ROUTINEroutine

ExplanationAn error occurred following invocation of a DDF exitroutine by Db2.

The variable "routine" is the name of the exit routine,DSNLHLIx, invoked by Db2.

System actionThe system abends the failing database-access agent.

DSNL800I csect-name EXECUTION FAILEDBECAUSE THE BIND DEPLOYFUNCTION IS NOT SUPPORTED BYTHE SERVER WHICH CAUSEDTERMINATION OF CONNECTION:LOCATION connection-location,PRODUCT ID product-identifier

ExplanationThe current BIND command failed because thecommand was routed to a server that does not supportthe bind deploy function.


connection-locationThe name of the server.

product-identifierAn alphanumeric string that identifies the product.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_roleofcdb.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_roleofcdb.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_populatecdbtcpip.html




AQT for IBM Db2 Analytics Accelerator for z/OSARI for DB2 Server for VSE & VMDSN for Db2 for z/OSHTP for non-secure HTTP URL connections forDb2 native REST servicesHTS for secure HTTPS connections for Db2native REST servicesJCC for IBM Data Server Driver for JDBC andSQLJQSQ for DB2 for iSQL for Db2 for Linux, UNIX, and Windows



5New-function mode.

System actionThe BIND command fails. The package is notdeployed.

Programmer responseEnsure that the database server is Db2 for z/OS DB2 9new-function mode or greater to support bind deployfunction.


Chapter 10. DSNM messagesMessage identifiers that begin with DSNM communicate information about the IMS attachment facility.

All DSNM messages are sent to the IMS master terminal operator (MTO) and to the appropriate MVSconsole.

DSNM001I IMS/TM ims/tm-nameCONNECTED TO SUBSYSTEMsubsystem-name

ExplanationThis is an information message only. The control regionof the specifiedIMS TM system successfully connectedto the specifiedDb2 subsystem.

ims/tm-nameThe name of theIMS TM system.

subsystem-nameThe name of the Db2 subsystem.

All DSNM messages are sent to the IMS masterterminal operator (MTO) and to the appropriate MVSconsole.

System actionIMS TM transactions can access Db2 resources.

DSNM002I IMS/TM ims/tm-nameDISCONNECTED FROMSUBSYSTEM subsystem-nameRC=reason-code

ExplanationThe specifiedIMS TM control region has disconnectedfrom the specified Db2 subsystem for the indicatedreason code.



reason-codeThe reason code:A

IMS TM is terminating normally (for example, /CKPT FREEZE command).

BIMS TM is terminating abnormally.

CDb2 is terminating in a quiesce fashion (forexample, Db2 stop quiesce command).

DDb2 is terminating abnormally.

EThe connection betweenIMS TM and the Db2subsystem is terminating; however, bothsubsystems remain operational.


System actionThe connection betweenIMS TM and Db2terminated.IMS TM transactions can no longer accessDb2 resources.


System programmer responseReason code A, C, or E makes this an informationmessage. Reason code D indicates that a seriousproblem occurred in the Db2 subsystem, and that theSYS1.LOGREC should be examined. For reason code Bor D, determine the failing subcomponent.


Problem determinationSYS1.LOGREC and/or dump information may beavailable for reason codes B and D.

DSNM003I IMS/TM ims/tm-name FAILED TOCONNECT TO SUBSYSTEMsubsystem-name RC=return-code

ExplanationThe specifiedIMS TM system control region did notconnect to the specified Db2 subsystem.






return-codeThe reason for the failure.00

The Db2 subsystem is not operational.However, a notify message has been queuedand, when the Db2 subsystem is started, it willautomatically connect toIMS TM.

04The connection attempt failed betweenIMS TMand the Db2 subsystem.


System actionIMS TM transactions cannot access Db2 resources.

Operator responseFor return code 00, start the Db2 subsystem. Forreturn code 04, notify the system programmer.

Problem determinationFor return code 04, anIMS TM attachment facility snaprecord (code X'5501FF') is written to theIMS TM log toindicate the reason for the failure.

Related tasksControlling CICS connections (Db2Administration Guide)Controlling IMS connections (Db2Administration Guide)Related informationRecovering Db2 when the CICS attachmentfacility cannot connect to Db2 (Db2Administration Guide)Recovering from IMS-related failures (Db2Administration Guide)

DSNM004I RESOLVE INDOUBT ENTRY(S) AREOUTSTANDING FOR SUBSYSTEMsubsystem-identifier

ExplanationThe subsystem-identifier subsystem has remainingindoubt entries after the IMS/TM subsystem hasattempted to resolve the work units that are indoubt.This message is sent to the IMS/TM master terminaloperator (MTO).

System actionThe connection between the Db2 and IMS/TMsubsystems remains active, and applications canaccess Db2 resources.


System programmer responseUse the DISPLAY THREAD and RECOVER INDOUBTcommands to display and resolve the work units thatare indoubt.

Problem determinationRecovery information is available on the Db2 log andIMS/TM log to assist in the resolution of the workunit(s) indoubt. For each indoubt work unit, an IMS/TMattachment facility snap record (code X'5501FE') iswritten to the IMS/TM log.

Related tasksResolving indoubt units of recovery (Db2Administration Guide)Related reference-DISPLAY THREAD (Db2) (Db2 Commands)-RECOVER INDOUBT (Db2) (Db2 Commands)

DSNM005I IMS/TM RESOLVE INDOUBTPROTOCOL PROBLEM WITHSUBSYSTEM subsystem-name

ExplanationThe specified subsystem has protocol incompatibilitieswithIMS TM. The Db2 resolve indoubt processreceived an unknown or invalid recovery request (RRE)fromIMS TM. The request was rejected by Db2 andkept byIMS TM.subsystem-name

The name of the subsystem.All DSNM messages are sent to the IMS masterterminal operator (MTO) and to the appropriate MVSconsole.

System actionThe connection between the Db2 andIMS TMsubsystems remains active, and applications canaccess Db2 resources.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_controlcicsconnections.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_controlcicsconnections.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_controlimsconnections.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_controlimsconnections.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recovercicsattachcantconnectdb2.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverimsfailures.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverimsfailures.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_resolveindoubtunits.html




System programmer responseCall IBM Support after extracting from theIMS TM logtheIMS TM attachment facility snap records (codeX'5501FE') using theIMS TM utility DFSERA10.

These records contain the complete request fromIMSTM to Db2, the request type is at offset X'01C', this is afour-character identifier which should contain any ofthe following words:

• 'SHOW'• 'IDBT'• 'COMM'• 'ABRT'

If theIMS TM recovery request (RRE) found in the log isan invalid one, (not 'COMM' or 'ABRT'), you maymanually delete it using the IMS/TM/CHANGE SUBSYSRESET command after consulting with the IBMSoftware Support.

If theIMS TM request is a valid one (abort or commit),you must find the action thatIMS TM performed forthat RRE by locating the X'3730' (commit) or X'3801'(abort) record in theIMS TM log and perform the sameaction under Db2 by using the -RECOVER INDOUBTcommand.

Problem determinationRecovery information is available on the Db2 log andIMS log to assist in the resolution of the problem. Foreach indoubt work unit, anIMS TM attachment facilitysnap record (code X'5501FE') is written to theIMS TMlog.

Related tasksResolving indoubt units of recovery (Db2Administration Guide)Related reference-RECOVER INDOUBT (Db2) (Db2 Commands)

DSNM100I SUBSYSTEM xxxx NOT AVAILABLE

ExplanationTheIMS TM command facility which routes commandsto the Db2 subsystem cannot perform its functionsbecause the Db2 subsystem named 'xxxx' isconsidered not operational.

System actionThe connection to the Db2 subsystem failed for thecommand. The command is rejected.

System programmer responseIf the Db2 subsystem is operational, and if you suspectan error in Db2, you might need to report theproblem.For information about identifying andreporting the problem, see Collecting diagnostic data(Collecting data). The person entering the request maynot be authorized to execute the command. If the Db2subsystem is not operational, Db2 commandsfromIMS TM cannot be processed.

Problem determinationA snap record (X'5501FF') is written to theIMS TM logif a connection request failed.

DSNM104I xxxx COMMAND FAILED

ExplanationThe Db2 command specified by xxxx failed tocomplete.

System actionThe command terminated without providing an outputmessage. Commands will still be allowed by theIMSTM attachment facility.


Problem determinationIf the command failed because of an abend, a snaprecord (X'5501FF') is written to theIMS TM log andSYS1.LOGREC information is available.

Chapter 10. DSNM messages 409









Chapter 11. DSNP messagesMessage identifiers that begin with DSNP communicate information about the data space manager.

The DSNP messages contain a connection ID, a correlation ID, and a logical-unit-of-work ID. Messagesthat have the same connection ID, correlation ID, and logical-unit-of-work ID relate to the same user. Thismakes it possible to scan a number of DSNP messages and group activities involving a given user.

DSNP001I csect-name - data-set-name ISWITHIN n BYTES OF AVAILABLESPACE. RC=reason-codeCONNECTION-ID=connection-identifier, CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=token

ExplanationThis message warns of an impending space shortage.The data space manager (DSM) extend function CSECT'DSNPmmmm' detected the space shortage throughthe use of a 'hedge' quantity n. Reason code reason-code gives some information about why space couldnot be obtained.

There might also be some preceding DSM and VSAMmessages that can help to determine why spacecannot be obtained. The connection, correlation, andlogical-unit-of-work IDs identify the user orapplication that encountered the problem. CorrelationIDs beginning with '0nn', where nnis a number, identifysystem agents.

A LUW-ID of an asterisk (*) indicates that the threaddoes not have a LUW-ID. If the LUW-ID is not anasterisk (*), the value is a logical-unit-of-work identifierthat is assigned to the thread followed by an equals (=)sign and a token value, which can be used in place oflogical-unit-of-work-id in any Db2 command thataccepts logical-unit-of-work-id as input.

Messages that have the same connection ID,correlation ID, and LUW-ID relate to the same user.This makes it possible to scan a number of DSNP-prefixed messages and group activities involving agiven user.

System actionIf sufficient space is available for the current request,continue. Otherwise, message DSNP007I follows, andthe current SQL request fails.

Operator responseDSM messages are directed to the databaseadministrator (DBA) or system administrator. However,the DBA or system administrator can request that the

operator issue an MVS WRITELOG operator command(for example, 'W A') to obtain MVS SYSLOG output. TheSYSLOG sometimes contains media managermessages that might be helpful to the DBA or systemadministrator in determining why space could not beallocated.

System programmer responseBased on the reason code (RC) in the message, as wellas information that might be available in accessmethod services or VSAM messages preceding thisone, try one of the following solutions:

• If you do not anticipate further extension of thistable space or index, ignore the message.

• If the table space or index is backed by storagegroup-defined data sets and this data set is not atmaximum extents, use the ALTER STOGROUPstatement to add volumes to the storage group (upto 133 of them).

• If the table space or index is backed by 'user-defined' data sets, and not at maximum extents forthe data set, issue an ALTER ADDVOLUMES accessmethod services command to provide additionalvolumes (up to 133 of them). Or, if the table space isnonpartitioned and the high allocated RBA is greaterthan or equal to 2GB (2,147,483,648) for theindicated data set, define the data set required forthe next sequential piece. (Actually, in this case,there should be an indication in console messages orthe reason code that the data set required for thenext piece was not found.)

• If the data set is at the maximum number of extents,recover or reorganize the table space or index aftertaking one of the following actions:

– Enlarge the primary or secondary space allocationquantity of the table space or index.

– If the Db2 subsystem is running on z/OS V1.7 orlater, and the data set is not shared with any z/OSsystems at an earlier level, convert the data set toSMS-managed with the Extent Constraint Removaloption set to YES in the SMS data class. If you dothis, the maximum number of extents is 7257.

• If all of the following conditions are true, themaximum number of extents is 7257:


– The z/OS level is V1.7 or later– The data set is SMS-managed– The Extent Constraint Removal option is set to

YES in the associated SMS data class• If any of the conditions outlined in the previous

bullet are not true, the maximum number of extentsis:

– 251 to 255 for non-striped data sets– 251 to 255 for each stripe for striped data sets

Problem determinationExamine the console messages, SYS1.LOGRECinformation, and SYSLOG to determine the reason forthe condition. Try to resolve it by the methodsdescribed in the Operator Response section of thismessage. If you feel that this message indicates aproblem in an IBM program, you should provide thefollowing sources of information about the problem:

• Console sheet showing the message and relatedmessages that might precede or follow it.

• System log printout (obtained via MVS WRITELOGoperator command) showing related VSAM/mediamanager messages that might appear there (usuallyneeded only if you have a message or reason codethat indicates a media manager services problemoccurred).

• Integrated catalog facility (ICF) catalog listingshowing characteristics of the data set in questionand of the ICF catalog itself.

• VTOC listing of packs associated with the request,showing space available for data sets, catalogs,VTOC index, and the VTOC itself, as well as data setextent information.

• Any associated dumps.• SYS1.LOGREC listing showing entries at or near the

time of the problem (unless these appear in anassociated dump).

• Depending on the reason code, the results of certainSQL SELECT operations on Db2 catalog tables maybe needed.

Related conceptsPrimary space allocation (Db2 AdministrationGuide)Example of primary and secondary spaceallocation (Db2 Administration Guide)Related tasksExtending user-managed data sets (Db2Administration Guide)Extending a data set (Db2 Administration Guide)Letting SMS manage your Db2 storage groups(Db2 Administration Guide)

DSNP002I csect - DEFINE FAILED FOR data-set-name RC=reason-codeCONNECTION-ID=connection-id,CORRELATION-ID=correlation-id,LUW-ID=logical-unit-of-work-id=token

ExplanationData set definition failed (in CSECT 'DSNPmmmm') forthe reason identified by RC. The connection ID,correlation ID, and logical-unit-of-work ID (LUW-ID)identify the user or application that encountered theproblem. The connection, correlation, and logical-unit-of-work IDs identify the user or application thatencountered the problem. Correlation IDs beginningwith '0nn', where 'nn' is a number, identify systemagents.

A LUW-ID of '*' indicates that the thread does not havea LUW-ID. If the LUW-ID is not an '*', the value is alogical-unit-of-work-id that is assigned to the threadfollowed by an '=' sign and a token value, which can beused in place of logical-unit-of-work-id in any Db2command that accepts logical-unit-of-work-id asinput.


System actionThe data space manager (DSM) terminates its actionsassociated with the current SQL request. Higher levelfunctions might terminate the current SQL request orthe unit of recovery that issued the request.

Operator responseThis message is directed to either the databaseadministrator or the system administrator. Bring themessage to their attention if it appears on the MVSoperator's console. The installation should considerdirecting Db2 messages to a console other than theoperator's console.

System programmer responseInvestigate the problem indicated by the reason codeand preceding access method services messages, ifany, and correct it, if possible. If an out-of-spacecondition exists, see the description of messageDSNP001I for actions to consider.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_allocationprimaryspace.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_spaceallocationexample.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_extenddatasets.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverextenddataset.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_letsmsmanagestoragegroups.html


Problem determinationSee Problem Determination of message DSNP001I forthis information.

Related conceptsDb2 reason codes (Db2 Codes)Related informationDSNP001Icsect-name - data-set-name IS WITHIN nBYTES OF AVAILABLE SPACE. RC=reason-codeCONNECTION-ID=connection-identifier,CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=token

DSNP003I csect - RESET FAILED FOR data-set-name. RC=rrrrrrrrCONNECTION-ID=xxxxxxxx,CORRELATION-ID=yyyyyyyyyyyy,LUW-ID=logical-unit-of-work-id=token

ExplanationReset, a data space manager (DSM) function invokedby Db2 utilities, failed in CSECT 'DSNPmmmm' for thereason identified by RC. The connection ID, correlationID, and logical-unit-of-work ID (LUW-ID) identify theuser or application that encountered the problem.Correlation IDs beginning with '0nn', where 'nn' is anumber, identify system agents.


Messages that have the same connection ID,correlation ID, and LUW-ID relate to the same user.This makes it possible to scan a number of DSNP-prefixed messages and tie together activities involvinga given user.

System actionDSM terminates its actions associated with the currentSQL request. Higher level functions might terminatethe current SQL request or the unit of recovery thatissued the request.

Operator responseThis message is directed to the database administratoror the system administrator. Bring it to that person'sattention if it appears on the MVS operator's console.The installation should consider directing Db2

messages to a console other than the operator'sconsole.

System programmer responseInvestigate the problem indicated by the reason codeand preceding Db2, access method services, or VSAMmessages, if any, and correct it, if possible.

It might be necessary to delete and redefine the dataset using access method services. Consider making abackup copy before doing this. (Use Db2 utilities tomake the copy; in general, VSAM utilities do not workon Db2 database services data sets.)

Problem determinationSee Problem Determination for message DSNP001I forthis information.


DSNP004I csect - DELETE FAILED FOR data-set-name. RC=reason-codeCONNECTION-ID=connection-id,CORRELATION-ID=correlation-id,LUW-ID=logical-unit-of-work-id=token

ExplanationDeletion failed in CSECT 'DSNPmmmm' for the reasonidentified by the RC=reason-code value. Theconnection ID, correlation ID, and logical-unit-of-workID (LUW-ID) identify the user or application thatencountered the problem. Correlation IDs beginningwith '0nn', where 'nn' is a number, identify systemagents.

The value of the LUWID is a logical-unit-of-work-idthat is assigned to the thread followed by an '=' signand a token value, which can be used in place oflogical-unit-of-work-id in any Db2 command thataccepts logical-unit-of-work-id as input.

Messages that have the same connection ID,correlation ID, and LUWID relate to the same user. Thismakes it possible to scan a number of DSNP-prefixedmessages and group activities involving a given user.

Chapter 11. DSNP messages 413



System actionDb2 terminates its actions associated with the currentSQL request. Db2 might terminate the current SQLrequest or the unit of recovery that issued the request.

Operator responseThis message is directed to the database administratoror the system administrator. Bring it to that person'sattention if it appears on the MVS operator's console.The installation should consider directing Db2messages to a console other than the operator'sconsole.

System programmer responseInvestigate the problem indicated by the reason codeand preceding access method services messages ifany, and correct it, if possible. Check the data set anddelete it by using access method services directly ifreasonable to do so. Consider making a backup copybefore doing this. (Use Db2 utilities to make the copy;in general, VSAM utilities do not work on Db2 datasets.)


Severity8 (error)


DSNP005I csect - COULD NOT REMOVEEXCESS VOLUMES FROMCANDIDATE LIST OF data-set-name CONNECTION-ID=xxxxxxxx,CORRELATION-ID=yyyyyyyyyyyy,LUW-ID=logical-unit-of-work-id=token

ExplanationVolumes from a storage group were entered in thedata set's candidate list and could not be removed byCSECT 'DSNPmmmm' after some data space manager

(DSM) operation. The connection ID, correlation ID,and logical-unit-of-work ID (LUW-ID) identify the useror application that encountered the problem.Correlation IDs beginning with '0nn', where 'nn' is anumber, identify system agents.



This is not a major problem. However, the data set willnot properly reflect subsequent deletions from thevolume list in its storage group (via ALTER STOGROUPcommand in SQL), because the data set's integratedcatalog facility (ICF) catalog entry still contains thevolume serial numbers.

If needed, the storage group in question can beidentified by issuing an SQL SELECT to get informationabout the table space or index that is identified by thethird and fourth qualifiers (database name, table spacename) in the data set name.

System actionOperation continues.


System programmer responseLook for associated DSM and access method servicesmessages preceding this one to get additionalinformation. Attempt an ALTER REMOVEVOLUMESaccess method services command, if appropriate, afterissuing a LISTCAT to see which volumes are recordedas 'candidate' in the integrated catalog facility (ICF)catalog.



Problem determinationSee Problem Determination for message DSNP001I forthis information. (However, there should not be a needfor VTOC or SYSLOG information for this case.)

DSNP006I csect - REQUIRED STOGROUPDEFINED DATA SET NOTAVAILABLE- data-set-nameRC=rrrrrrrr CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-work-id=token

ExplanationAn attempt to alter the shareoptions of this data setfailed. The data set could not be accessed for thereason indicated by RC. The connection ID, correlationID, and logical-unit-of-work ID (LUWID) identify theuser or application that encountered the problem.Correlation IDs beginning with '0nn', where 'nn' is anumber, identify system agents.

The value of the LUWIDis a logical-unit-of-work-id thatis assigned to the thread followed by an '=' sign and atoken value, which can be used in place of the logical-unit-of-work-id in any Db2 command that accepts thelogical-unit-of-work-id as input.

Messages having the same connection ID, correlationID, and LUWID relate to the same user. This makes itpossible to scan a number of DSNP-prefixed messagesand group activities involving a given user.





Severity8 (error)


DSNP007I csect-name - EXTEND FAILED FORdata-set-name. RC=reason-codeCONNECTION-ID=connection-id,CORRELATION-ID=correlation-id,LUW-ID=logical-unit-of-work-id =token

ExplanationExtension failed in control section DSNPmmmm of thedata space manager (DSM). The data-set-name valueidentifies the data set that is being extended. Thereason-code value is the reason code, which indicateswhy the extend process failed. The connection-id,correlation-id, and logical-unit-of-work-id valuesidentify the user or application that encountered theproblem. Correlation identifiers begin with '0nn', wherenn is a number that identifies system agents.

When the logical-unit-of-work-id value is '*' (asterisk)the thread does not have a LUWID. If the logical-unit-of-work-id value is not '*', the logical-unit-of-work-idvalue is a logical unit of work identifier (LUWID) that isassigned to the thread, followed by an '=' (equal sign)and a token value, which can be used in place of theLUWID in any Db2 command that accepts the LUWIDvalue as input.

Messages that have the same connection-id,correlation-id, and logical-unit-of-work-id values relateto the same user. This situation makes it possible toscan a number of DSNP-prefixed messages and groupactivities involving a given user.

System actionThe DSM terminates its actions associated with thisextend request. Higher level functions might terminateif they cannot continue without a successful extend. Inthis case, additional console messages and/or SQL





codes are produced. In other cases, higher levelfunctions might be able to resolve the space needwithout the extend, so they continue normally.

Operator responseSee Operator Response for message DSNP001I forthis information.

System programmer responseThe following sources of information are available tohelp determine the cause of the failure:

• See the Programmer Response for messageDSNP001I.

• Analyze the reason-code value in conjunction withthe console messages.

• The reason code might apply to the data setidentified in the message or to another data set thatis needed for the extend process. If the reason codeindicates a data set access failure, the consolemessages indicate the data set name. For example, ifthe RC indicates 'resource unavailable', consolemessages identify the resource that is unavailable.Most likely, the message is DSNT500I.

• Retrieve diagnostic information from the output ofthe DISPLAY DB...RESTRICT or DISPLAYUTIL(*)... commands.

• For information about finding the system diagnosticwork area (SDWA), see The system diagnostic workarea (SDWA) (Diagnosing Db2 problems).

Problem determinationSee Problem Determination for message DSNP001I.

Related conceptsDSNP messagesMessage identifiers that begin with DSNPcommunicate information about the data spacemanager.Db2 reason codes (Db2 Codes)Recovery of catalog and directory tables (Db2Administration Guide)Related tasksUsing disk space effectively (Db2 Performance)Improving the performance of sort processing(Db2 Performance)Recovering catalog and directory objects (Db2Utilities)Displaying threads by LUWID (Db2Administration Guide)Related referenceDb2 catalog tables (Db2 SQL)

-DISPLAY UTILITY (Db2) (Db2 Commands)-DISPLAY DATABASE (Db2) (Db2 Commands)Related informationDSNP001Icsect-name - data-set-name IS WITHIN nBYTES OF AVAILABLE SPACE. RC=reason-codeCONNECTION-ID=connection-identifier,CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=token

DSNP008I csect-name- REQUIRED USER-DEFINED DATA SET NOTAVAILABLE-data-set-nameRC=reason-code CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id=token

ExplanationOne of the following actions applied against user-defined data sets failed in CSECT 'DSNPmmmm' of thedata space manager (DSM):

• Create table space or index• Extend table space or index• Process the SQL ALTER DATABASE statement• Process the REORG TABLESPACE utility with

SHRLEVEL REFERENCE or CHANGE

Correlation IDs beginning with '0nn', where 'nn' is anumber, identify system agents.

One or more of the data sets could not be accessed forthe reason indicated by RC. The connection ID,correlation ID, and logical-unit-of-work ID (LUWID)identify the user or application that encountered theproblem.

The value of the LUWID is alogical-unit-of-work-id thatis assigned to the thread followed by an '=' sign and atoken value, which can be used in place of logical-unit-of-work-id in any Db2 command that accepts logical-unit-of-work-id as input.

Messages having the same connection ID, correlationID, and LUWID relate to the same user. This makes itpossible to scan a number of DSNP-prefixed messagesand group activities involving a given user.

If the name of the data set in the message is differentfrom the name of the original data set (for example,'....A002' instead of '...A001'), a new data set mightneed to be created. A different name indicates that theoriginal data set exceeded its limit.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_trbshootsystemdiagnosticworkarea.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_trbshootsystemdiagnosticworkarea.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_recovercatalogdirectorytables.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_recovercatalogdirectorytables.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_usediskspaceeffectively.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_improvesortprocessing.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_improvesortprocessing.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_recovercatalogdirectoryobjects.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_recovercatalogdirectoryobjects.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_catalogtablesintro.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_displayutility.html


System actionDb2 terminates its actions associated with the currentSQL request or utility. Db2 might terminate the currentSQL request or utility or the unit of recovery thatissued the request.


System programmer responseThe return code description might indicate that one ofthe following actions needs to be performed or itindicates the necessary steps:

• If the data set does not exist, create it beforeattempting the create table space/index or extenddata set again.

• If the data set shareoptions are incorrect, modify theshareoptions with access method services (AMS).

• The appropriate AMS command is ALTERSHAREOPTIONS.


Severity8 (error)


DSNP009I THE FOLLOWING ERRORMESSAGES WERE RECEIVED FORoperation ON data-set-name

DSNP010I END OF ERROR MESSAGES.CONNECTION-ID=xxxxxxxx,CORRELATION-ID=yyyyyyyyyyyy,LUW-ID=logical-unit-of-work-id=token

ExplanationMessages DSNP009I and DSNP010I enclose a blockof messages that are received by the data spacemanager (DSM) subcomponent of Db2 in response toan access method services (AMS) operation.operation

The access method services operation that wasbeing performed.

data-set-nameThe data set on which the operation was beingperformed.

The prefix of the messages in the block is usually IDC(access method services messages). However, theprefix can also be IKJ (dynamic allocation) or othersystem subcomponent IDs. Refer to the appropriateMVS publication for descriptions of the enclosedmessages.

The operation can be DEFINE CLUSTER, ALTERADDVOLUMES, ALTER REMOVEVOLUMES, ALTERNEWNAME, or DELETE CLUSTER. One or more otherDSM messages follow this message to explain whathappened as a result of the failure of this accessmethod services request. The connection ID,correlation ID, and logical-unit-of-work ID (LUW-ID)identify the user or application that encountered theproblem.


Messages that have the same connection ID,correlation ID, and LUW-ID relate to the same user.This makes it possible to scan a number of DSNP-prefixed messages and group activities involving agiven user. Correlation IDs beginning with '0nn', where'nn' is a number, identify system agents.





System programmer responseUse this information to help resolve problemsindicated by other DSM messages that follow this one.


DSNP011I csect-name - MEDIA MANAGERSERVICES ERROR FOR data-set-name. MMRC=ccccccccDSMRC=ffffffff CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id =token

ExplanationThe MMRC is the return code that Db2 received frommedia manager services. Refer to the appropriate MVSpublication for a description of these codes. DSMRC isa DSM reason code that indicates which of the mediamanager services functions, update or extend, failed.The message is from CSECT 'DSNPmmmm' of the dataspace manager (DSM). The connection ID, correlationID, and logical-unit-of-work ID (LUW-ID) identify theuser or application that encountered the problem.Correlation IDs beginning with '0nn', where nn is anumber, identify system agents.



System actionThe DSM terminates its actions associated with thecurrent SQL request. Higher level functions mightterminate the current SQL request or the unit ofrecovery that issued the request.

Operator responseDSM messages are directed to either the databaseadministrator (DBA) or the system administrator.However, they can request that the operator issue anMVS WRITELOG operator command (for example, 'W

A') to obtain MVS SYSLOG output. The SYSLOGsometimes contains media manager messages thatmight be helpful to the DBA or system administrator indetermining why space could not be allocated.

System programmer responseThis message might be preceded by one or more IECor ICY messages on the console or in SYSLOG. Thesemessages help to determine what happened and whataction to take.



DSNP012I csect - ERROR IN ICF CATALOGLOCATE FUNCTION FOR data-set-name CTLGRC=ccCTLGRSN=zzzzrrss CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=luw-id

Explanationcsect-name


data-set-nameThe name of the data set

ccThe return code that Db2 received from an SVC 26call (ICF catalog locate function).

zzzzrrssThe reason code that Db2 received from an SVC 26call (ICF catalog locate function). The reason codeis in the same format as that returned to Db2 bythe SVC 26 call.

If cc is 4 or 8, the reason code is associated withaccess method services message IDC3009I. Todetermine the name of the CSECT that set thereason code, convert zzzz from hexadecimal toEBCDIC, and append the resulting 2 characters to'IGG0CL'. For example, suppose that zzzz is C6C6.



The EBCDIC equivalent of X'C6C6' is 'FF', so theCSECT that set the reason code is IGG0CLFF.

rr is the hexadecimal equivalent of the reason codevalue that is documented in access methodservices message IDC3009I. ss is the hexadecimalequivalent of the return code value that isdocumented in access method services messageIDC3009I. (The return code follows the reasoncode.) Convert rr and ss to decimal. Then, see thedescription of IDC3009I for explanations of thereason code and return code. For example,suppose that rrss is 0532. The decimal equivalentof X'32' is 50, and the decimal equivalent of X'05'is 5. Therefore, in IDC3009I, you need to look up areturn code of 50 and a reason code of 5.

If CTLGRC=AAAAAA08 and CTLGRSN=AAAAAA08,zzzzrrss is not associated with access methodservices message IDC3009I. AAAAAA08 indicatesthat the specified data set is not in the ICF catalog.

xxxxxxxxThe connection ID for the user or application thatencountered the problem.

yyyyyyyyyyyyThe correlation ID for the user or application thatencountered the problem.

Correlation IDs that begin with '0nn', where nn is anumber, identify system agents.

luw-idThe logical unit of work (LUW) ID for the user orapplication that encountered the problem.

An LUW ID with an asterisk (*) indicates that thethread does not have an LUW ID. If the LUW ID isnot an asterisk (*), the value is an LUW ID that isassigned to the thread followed by an equals sign(=) and a token value. (The token value can beused in place of the LUW ID in any Db2 commandthat accepts an LUW ID as input.)

Messages that have the same connection ID,correlation ID, and LUW ID relate to the same user.This situation makes it possible to scan a number ofDSNP messages and group activities that involve aparticular user.

System actionDb2 terminates its actions that are associated with thecurrent SQL request. Higher-level functions mightterminate the current SQL request or the unit ofrecovery that issued the request.

System programmer responseCorrect the problem that is indicated by the catalogreturn and reason codes.


Related referenceMessage IDC3009I (MVS System Messages)Related informationDSNP001Icsect-name - data-set-name IS WITHIN nBYTES OF AVAILABLE SPACE. RC=reason-codeCONNECTION-ID=connection-identifier,CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=tokenReturn Codes from CATALOG (DFSMSdfpAdvanced Services)

DSNP013I INSUFFICIENT PRIMARYALLOCATION SPACE TO FORMATCONTROL PAGES IN DATA SETdata-set-name CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-work-id =token

ExplanationData space manager (DSM) discovered that theprimary space quantity given in the data set definitionwas not large enough. Formatting of required controlinformation in the first several pages was not possible.The connection ID, correlation ID, and logical-unit-of-work ID (LUW-ID) identify the user or application thatencountered the problem.





http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieam600/bb3009i.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idas300/rcat.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idas300/rcat.htm


System programmer responseThis should occur only for table spaces or indexes thatare not storage group defined. (The Db2 interpreterforces the initial allocation to be large enough if astorage group is used.) Check both the page sizespecification (4KB or 32KB) and the number of controlpages required (2 for table space, 3 for index space).Specify the primary allocation value again so that atleast (pages multiplied by page size) bytes areallocated.


DSNP014I IRLM MANUAL LOCK REQUESTFAILED FOR data-set-name.RC=reason-code,SC=subcode,CONNECTION-ID=connection-id,CORRELATION-ID=correlation-id,LUW-ID=logical-unit-of-work-id=token

ExplanationDb2 requested a manual lock on a data set, but thelock could not be obtained for reasons specified in RCand SC. RC and SC are the return code and reasoncode from IRLM. The connection ID, correlation ID,and logical-unit-of-work ID (LUW-ID) identify the useror 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 possible to scan a number of DSNP-prefixed messages and group activities involving agiven user. DSNP001I or DSNP007I follow thismessage. Correlation IDs beginning with '0nn', where'nn' is a number, identify system agents.

If message DSNT376I was received before messageDSNP014I, the lock request failed because of atimeout condition. Otherwise, refer to the IRLM returnand reason codes for an explanation of the failure.

System actionThe current SQL or the unit of recovery that issued therequest might be terminated.


System programmer responseInvestigate the problem indicated by the IRLM returnand reason code.

Problem determinationProvide the console sheet and a dump. A GTF tracemight also be required. If you suspect an error in Db2,you might need to report the problem. For informationabout identifying and reporting the problem, seeCollecting diagnostic data (Collecting data). Refer tothe explanation section of this message for additionalproblem determination information.

Related conceptsIRLM return and reason codes (IRLM)Related informationDSNP001Icsect-name - data-set-name IS WITHIN nBYTES OF AVAILABLE SPACE. RC=reason-codeCONNECTION-ID=connection-identifier,CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=tokenDSNP007Icsect-name - EXTEND FAILED FOR data-set-name. RC=reason-code CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id = tokenDSNT376IPLAN=plan-name1 WITH CORRELATION-ID=correlation-id1 CONNECTION-ID=connection-id1 LUW-ID=luw-id1 THREAD-INFO=thread-information1 IS TIMED OUT. ONEHOLDER OF THE RESOURCE IS PLAN=plan-name2 WITH CORRELATION-ID=correlation-id2CONNECTION-ID=connection-id2 LUW-ID=luw-




id2 THREAD-INFO= thread-information2 ONMEMBER member-name

DSNP015I csect - IRLM MANUAL UNLOCKREQUEST FAILED FOR data-set-name. RC=reason-code,SC=sub-code, CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id=token

ExplanationDb2 requested a manual unlock on a data set, but theunlock could not be performed for reasons specified inRC and SC. The connection ID, correlation ID, andlogical-unit-of-work ID (LUW-ID) identify the user orapplication that encountered the problem.



System actionThe current SQL or the unit of recovery that issued therequest might be terminated.


System programmer responseInvestigate the problem indicated by the IRLM returnand reason code.

Problem determinationProvide the console sheet and a dump. A GTF tracemight also be required. If you suspect an error in Db2,you might need to report the problem. For informationabout identifying and reporting the problem, see

Collecting diagnostic data (Collecting data). See theexplanation section of this message for additionalproblem determination information.

Related conceptsIRLM return and reason codes (IRLM)

DSNP016I CREATE FAILED FOR pageset-name. RC=rrrrrrrr CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-work-id =token

ExplanationCreation of a table space or index space failed in thedata space manager (DSM) for the reason given in RC.The format of the pageset-name value isdbname.tiname.instance, where dbname is thedatabase name and tiname is the table space or indexspace name.

This message identifies the function that was inprogress at the time of a failure. The specific failure isusually identified by a preceding message. Theconnection ID, correlation ID, and logical-unit-of-workID (LUW-ID) identify the user or application thatencountered the problem.








System programmer responseInvestigate the problem indicated by reason code andpreceding messages, and correct it, if possible.



DSNP017I RESET FAILED FOR pageset-name.RC=reason-code CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id =token

ExplanationReset failed in the data space manager (DSM)subcomponent of Db2 for a table space or index spacefor the reason that is indicated by the RC=reason-codevalue.) The format of the pageset-name value isdbname.tiname, where dbname is the database nameand tiname is the table space or index space name.

This message identifies the function that was inprogress at the time of a failure. The specific failure isusually identified by a preceding message. Theconnection ID, correlation ID, and logical-unit-of-workID (LUW-ID) identify the user or application thatencountered the problem.





System programmer responseInvestigate the problem indicated by the reason codeand preceding messages, and correct it, if possible.



DSNP018I DROP FAILED FOR pageset-name.RC=reason-code CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id =token

ExplanationDrop failed in the data space manager (DSM)subcomponent of Db2 for a table space or index spacefor the reason given in RC. The format of the pageset-name value is dbname.tiname, where dbname is thedatabase name and tiname is the table space or indexspace name. This message identifies the function thatwas in progress at the time of a failure. The specificfailure is usually identified by a preceding message.The connection ID, correlation ID, and logical-unit-of-work ID (LUW-ID) identify the user or application thatencountered the problem.

A LUW-ID of '*' indicates that the thread does not havea LUW-ID. If the LUW-ID is not an '*', the value is alogical-unit-of-work-id that is assigned to the thread




followed by an '=' sign and a token value, which can beused in place of logical-unit-of-work-id in any Db2command that accepts logical-unit-of-work-id asinput.




System programmer responseInvestigate the problem indicated by the reason codeand preceding messages, and correct it, if possible.



DSNP019I csect-name - REALLOCATE FAILEDFOR data-set-name. RC=reason-code CONNECTION-ID=connection-id, CORRELATION-ID=correlation-id, LUW-ID=logical-unit-of-work-id=token

ExplanationAfter a successful ALTER REMOVE VOLUMES request,the data space manager (DSM) subcomponent of Db2was unable to reallocate the data set for the reasonindicated by the RC=reason-code value. Theconnection ID, correlation ID, and logical-unit-of-workID (LUW-ID) identify the user or application thatencountered the problem.




Operator responseThis message is directed to the database administratoror the system administrator. Bring it to that person'sattention if it appears on the MVS operator's console.

System programmer responseThe data set and corresponding page set piece orpartition can usually continue to be used by the Db2subsystem. However, they should be stopped andrestarted at the earliest possible time in order tosynchronize the allocation control blocks with theintegrated catalog facility (ICF) catalog volume list.


Related conceptsDb2 reason codes (Db2 Codes)Related tasksAdding or removing volumes from a Db2 storagegroup (Db2 Administration Guide)Related informationDSNP001Icsect-name - data-set-name IS WITHIN nBYTES OF AVAILABLE SPACE. RC=reason-codeCONNECTION-ID=connection-identifier,




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_addremovestoragevolumes.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_addremovestoragevolumes.html

CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=token

DSNP020I csect-name - USER DEFINEDATTRIBUTES INCORRECT FORdata-set-name. RC=reason-codeCONNECTION-ID=connection-identifier, CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id =token

ExplanationThe specified data set was access method servicesuser-defined and does not have the required Db2attributes. The connection ID, correlation ID, andLUWID values identify the user or application thatencountered the problem.

The value of the LUWID is a logical unit of workidentifier that is assigned to the thread, followed by an'=' sign and a token value, which can be used in placeof 'logical-unit-of-work-id' in any Db2 command thataccepts 'logical-unit-of-work-id' as input.

Messages having the same connection ID, correlationID, and LUWID relate to the same user. This makes itpossible to scan a number of DSNP-prefixed messagesand group activities involving a given user. CorrelationIDs beginning with '0nn', where 'nn' is a number,identify system agents.

System actionNo action is taken with the named data set. An errorcode is returned and a dump is not taken.


System programmer responseDelete the named data set and define it with thecorrect attributes.

Problem determinationObtain an access method services LISTCAT for thenamed data set's attributes.

Severity8 (error)

Related tasksDefining data sets (Db2 Administration Guide)Displaying threads by LUWID (Db2Administration Guide)

Related referenceData set naming conventions (Db2Administration Guide)

DSNP021I csect-name EXTEND NOTIFYFAILED FOR data-set-name,SC=ssssssss, NOTESC=nnnnnnnn,CONNECTION-ID=xxxxxxxx,CORRELATION-ID=yyyyyyyyyyyy,LUW-ID=logical-unit-of-work-id=token

ExplanationThis is an internal error. The connection ID, correlationID, and logical-unit-of-work ID (LUW-ID) identify theuser or application that encountered the problem.

An LUW-ID of '*' indicates that the thread does nothave an LUW-ID. If the LUW-ID is not an '*', the value isa logical-unit-of-work-id that is assigned to the threadfollowed by an '=' sign and a token value, which can beused in place of the logical-unit-of-work-id in any Db2command that accepts the logical-unit-of-work-id asinput.


If message DSNT376I was received before messageDSNP021I, the notify request failed because of atimeout condition.

System actionThe current SQL statement or the unit of recovery thatissued the request might be terminated.

Problem determinationObtain the console sheet and a dump. A GTF tracemight also be required.


DSNP022I csect-name EXTEND DBETRECORDING FAILED FOR data-set-name, RC=rrrrrrrr, SC=ssssssss,DBETSC=nnnnnnnn,CONNECTION-ID=xxxxxxxx,CORRELATION-ID=yyyyyyyyyyyy,LUW-ID=logical-unit-of-work-id=token


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_definedatasets.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_datasetnamingconventions.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_datasetnamingconventions.html



ExplanationThis is an internal error. The connection ID, correlationID, and logical-unit-of-work ID (LUW-ID) identify theuser or application that encountered the problem.

An LUW-ID of '*' indicates that the thread does nothave an LUW-ID. If the LUW-ID is not an '*', the value isa logical-unit-of-work-id that is assigned to the threadfollowed by an '=' sign and a token value, which can beused in place of the logical-unit-of-work-id in any Db2command that accepts the logical-unit-of-work-id asinput.


System actionThe current SQL statement or the unit of recovery thatissued the request might be terminated.

Problem determinationObtain the console sheet and a dump. A GTF tracemight also be required.


DSNP026I csect-name DATASET IS NOTALLOWED TO BE DELETED data-set-name, RC=rrrrrrrr,CONNECTION-ID=xxxxxxxx,CORRELATION-ID=yyyyyyyyyyyy,LUW-ID=logical-unit-of-work-id=token

ExplanationDuring clean up of the shadow data set in the final stepof online REORG, an error is detected due to anattempt to delete a regular table or index space dataset. The connection ID, correlation ID, and logical unitof work ID (LUWID) identify the user or applicationthat encountered the problem. Correlation IDsbeginning with '0nn', where 'nn' is a number, identifysystem agents.

The value of the LUWID is assigned to the threadfollowed by an '=' sign and a token value, that can beused in place of the LUWID in any Db2 command thataccepts it as input.


System actionNo action is taken with the named data set. An errorcode is returned and a dump is not taken.


System programmer responseDetermine the failing environment. If you suspect anerror in Db2, you might need to report the problem.For information about identifying and reporting theproblem, see Collecting diagnostic data (Collectingdata).

Problem determinationThis is an internal error in the online REORG of utility.For more information about this type of error, seemessage DSNP001I.

Related referenceREORG TABLESPACE (Db2 Utilities)REORG INDEX (Db2 Utilities)Related informationDSNP001Icsect-name - data-set-name IS WITHIN nBYTES OF AVAILABLE SPACE. RC=reason-codeCONNECTION-ID=connection-identifier,CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=token

DSNP027I csect-name RENAME FAILED OLDDATASET=data-set-name, NEWDATASET=data-set-name,RC=rrrrrrrr, CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-work-id=token

ExplanationAn attempt to alter the data set name failed. Theconnection ID, correlation ID, and logical unit of workID (LUWID) identify the user or application thatencountered the problem. Correlation IDs beginningwith '0nn', where 'nn' is a number, identify systemagents.

The value of the LUWID is assigned to the threadfollowed by an '=' sign and a token value, that can be






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_reorgtablespace.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/ugref/src/tpc/db2z_utl_reorgindex.html

used in place of the LUWID in any Db2 command thataccepts it as input.





Problem determinationSee 'Problem Determination' for message DSNP001Ifor this information.

Severity8 (error)

DSNP028I csect-name HSM RECALL FAILEDFOR DSNAME = dsnHSMRC=rrrrrrrr,HSMRSN=ssssssssCONNECTION ID=xxxxxxxx,CORRELATION ID=yyyyyyyyyyyy,LUW-ID=logical-unit-of-work-id=token

ExplanationThis message indicates that a required data set wasmigrated by HSM and an attempt to recall the data setfailed, preventing Db2 from accessing the data set.The HSMRC and HSMRSN fields can be used todetermine the HSM failure. See ProblemDetermination below. The connection ID, correlationID, and 'logical-unit-of-work ID' (LUW-ID) identify theuser or application that encountered the problem.

A LUW-ID of '*' indicates that the thread does not havea LUW-ID. If the LUW-ID is not an '*', the value is a'logical-unit-of-work-id' that is assigned to the threadfollowed by an '=' sign and a token value, which can beused in place of 'logical-unit-of-work-id' in any Db2command that accepts 'logical-unit-of-work-id' asinput.


System actionDSM terminates its action with the associated data set.Higher level functions that issued the recall requestmight terminate.


System programmer responseInvestigate the reason for the HSM recall failure. Usethe information in this message to help resolve thisproblem. Additional messages on the MVS operator'sconsole might be associated with this message.

Problem determinationIf the HSMRSN is 999, refer to the following list for theexplanation:HSMRC

Description4

HSM is not active.8

No storage is available for MWE in CSA.36

Input MWE is not within user storage.40

Allocated amount of CSA for MWEs was exceeded.100

There was an invalid function used.

For all other reason codes (HSMRSN), refer to the z/OSDFSMShsm Managing Your Own Data for anexplanation of HSM user messages. The HSM usermessages can be determined by appending the valuein the HSMRC field of this message to ARC1100I (thatis, HSMRC=12, HSM message is ARC1112I). TheHSMRSN reason code is referenced in the ARC1100Imessages.




DSNP030I csect-name THE CURRENT EXTENTREACHES THE LAST VOLUME FORdata-set-name. CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-work-id=token

ExplanationThis message indicates that the last volume to whichthe data set data-set-name can extend has beenreached. You cannot add more volumes if the currentvolume runs out of space.

The connection, correlation, and logical-unit-of-workIDs identify the user or application that encounteredthe problem. Correlation IDs beginning with '0nn',where 'nn' is a number, identify system agents.



System actionIf sufficient space in current volume is available for thecurrent request, Db2 continues. Otherwise, messageDSNP007I is issued, and the current SQL request fails.

Operator responseFor more information, issue an MVS WRITELOGoperator command (for example, 'W A') to obtain MVSSYSLOG output. The SYSLOG sometimes containsVSAM or media manager messages that might behelpful in determining why space could not beallocated.

System programmer responseDepending on what information is available in theaccess method services or VSAM messages precedingthis one, try one of the following:


• If the table space or index is backed by SMS-managed data sets, use LISTCAT to choose anotherSMS storage group that has more space available

and recover or reorganize the table space or indexinto the new SMS storage group.

• If the table space or index is Db2-managed but is notSMS-managed, rearrange the Db2 storage groupvolume list by shifting volumes with free space or byadding new volumes. Use the SQL statements ALTERSTOGROUP ADD VOLUMES and ALTER STOGROUPREMOVE VOLUMES and then recover or reorganizethe table space or index.

• If the table space or index is user-managed and notSMS-managed, delete and redefine the data set withmore space and then recover or reorganize the tablespace or index.

Problem determinationObtain an access method services LISTCAT for thenamed data set's VOLUME list for current extent spacedistribution of volumes.

See the Problem Determination section of messageDSNP001I for more information.


DSNP031I csect-name - CURRENT SPACEHAS nn EXTENTS FOR data-set-name. THE MAXIMUM EXTENTS ISmm. CONNECTION-ID=connection-identifier, CORRELATION-ID=-correlation-identifier, LUW-ID=logical-unit-of-work-id=token

ExplanationThis message indicates that data set data-set-namehas almost reached the maximum number of extents.The maximum number is indicated by mm. You cannotadd more volumes if the current volume runs out ofspace.

The connection, correlation, and logical-unit-of-workIDs identify the user or application that encounteredthe problem. Correlation IDs beginning with 0nn(where nn is a number) identifies system agents.

A LUW-ID of an asterisk (*) indicates that the threaddoes not have a LUW-ID. If the LUW-ID is not anasterisk (*), the value is a logical-unit-of-work-id that isassigned to the thread followed by an equals sign (=)and a token value, which can be used in place oflogical-unit-of-work-id in any Db2 command thataccepts logical-unit-of-work-id as input.

Messages that have the same connection ID,correlation ID, and LUW-ID relate to the same user.Including all three pieces of information makes it


possible to scan a number of DSNP-prefixed messagesand group activities involving a given user.

System actionDb2 continues. If the table space or index space is notable to extend when needed, Message DSNP001I isissued and the current SQL request fails.

Operator responseFor more information, issue an MVS WRITELOGoperator command (for example, 'W A') to obtain MVSSYSLOG output. The SYSLOG sometimes containsVSAM or media manager messages that might behelpful in determining why space could not beallocated.

System programmer responseBased on the information that might be available in theaccess method services or VSAM messages precedingthis one, try one of the following actions:


• If the table space or index is Db2-managed and hasnot yet reached the maximum number of extents,obtain an access method services LISTCAT for thenamed data set's to see how the extensions aredistributed. Your options then include:

– If there are multiple small extents, you can usethe SQL statement ALTER TABLESPACE SECQTY toalter to a larger secondary space allocationquantity.

– Otherwise, use the ALTER STOGROUP statementto add volumes to the storage group (up to 133 ofthem).

• If the table space or index is user-managed and hasnot yet reached the maximum number of extents,issue the access method services command ALTERADDVOLUMES to provide additional volumes (up to59 of them).

• If the data set is at the maximum number of extents,recover or reorganize the table space or index aftertaking one of the following actions:

– Enlarge the primary or secondary space allocationquantity of the table space or index.

– If the Db2 subsystem is running on z/OS V1.7 orlater, and the data set is not shared with any z/OSsystems at an earlier level, convert the data set toSMS-managed with the Extent Constraint Removaloption set to YES in the SMS data class. If you dothis, the maximum number of extents is 7257.

Problem determinationObtain an access method services LISTCAT for thenamed data set's VOLUME list for the extent spacedistribution.

See the Problem Determination section of messageDSNP001I for more information.


Related conceptsPrimary space allocation (Db2 AdministrationGuide)Example of primary and secondary spaceallocation (Db2 Administration Guide)Related tasksExtending user-managed data sets (Db2Administration Guide)Extending a data set (Db2 Administration Guide)Letting SMS manage your Db2 storage groups(Db2 Administration Guide)Related referenceALTER TABLESPACE (Db2 SQL)ALTER STOGROUP (Db2 SQL)Related informationDSNP001Icsect-name - data-set-name IS WITHIN nBYTES OF AVAILABLE SPACE. RC=reason-codeCONNECTION-ID=connection-identifier,CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=token








https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverextenddataset.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_altertablespace.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sql_alterstogroup.html

Chapter 12. DSNQ messagesMessage identifiers that begin with DSNQ communicate information about MQListener.

DSNQ001I MQListener was invoked with nomajor function on the commandline.

ExplanationThe MQListener command line failed to specify a majorfunction, such as help, run, add, remove, or show.

User responseConsult MQListener documentation and re-runMQListener with the function that was intended. Formore information, run:

• db2mqln1/db2mqln2 help

Severity8 (Error)

DSNQ002I MQListener was invoked with anunknown command line parameterparameter-name.

ExplanationThe MQListener command line contained an unknownparameter parameter-name.

User responseConsult MQListener documentation and rerunMQListener with the correct parameters. For moreinformation, run


Severity8 (Error)

DSNQ003I MQListener was invoked withoutthe required command lineparameter parameter name.

ExplanationThe MQListener command line was missing theparameter parameter name, which was required.

User responseConsult MQListener documentation and re-runMQListener with the parameter that was required. Formore information, run


Severity8 (Error)

DSNQ004I MQListener was invoked with anillegal value for the parametername command line parameter:parameter value.

ExplanationThe MQListener command line contained an illegalvalue for the parameter name parameter. The illegalvalue was parameter value.

User responseConsult MQListener documentation and re-runMQListener with the correct parameters. For moreinformation, run


Severity8 (Error)

DSNQ010I MQListener encountered adatabase error accessingsubsystem subsystem name duringoperation operation name: sqlstate= sqlstate value (sqlcode = sqlcodevalue).

ExplanationMQListener encountered a Db2 database erroraccessing subsystem subsystem name while executingoperation operation name. The resulting sqlstate wassqlstate value (sqlcode sqlcode value).

User responseConsult MQListener documentation and ensure thatMQListener is properly installed in the specified Db2subsystem and access to MQListener packages and


configuration tables ahs been granted to the userrunning MQListener.

Severity8 (Error)

DSNQ011I MQListener failed to make RRSconnection to the subsystemsubsystem name during operationoperation name: reason code =reason code value ( return code =return code value ).

ExplanationMQListener encountered a Db2 database error whileattempting to connect to subsystem subsystem nameduring operation operation name. The resulting reasoncode was reason code value ( return code return codevalue).

User responseEnsure that the Db2 subsystem subsystem name isactive and running.

Severity8 (Error)

DSNQ012I MQListener failed to terminateRRS connection from thesubsystem subsystem name duringoperation operation name: reasoncode = reason code value ( returncode = return code value ).

ExplanationMQListener encountered a Db2 database error whileattempting to disconnect from subsystem subsystemname during operation operation name. The resultingreason code was reason code value ( return codereturn code value).

User responseEnsure that the Db2 subsystem subsystem name isactive and running. Consult the Db2 documentation,regarding the exact meaning of the reason and returncode.

Severity4 (Warning)

DSNQ020I MQListener encountered a MQerror error executing operation

operation name on object objectname in queue manager queuemanager name: reason code =reason code value.

ExplanationMQListener encountered a MQ error error whileexecuting operation operation name on object objectname in queue manager queue manager name. Theresulting reason code was reason code value.

User responseEnsure that IBM MQ is properly installed andconfigured, and accessible to the user runningMQListener. Consult the IBM MQ documentation formore information, particularly the ApplicationProgramming Reference for more information aboutthe reason code.

Severity8 (Error)

DSNQ021I MQListener failed to connect to MQqueue manager queue managername: reason code = reason codevalue.

ExplanationMQListener encountered a MQ error error whileattempting to connect to MQ queue manager queuemanager name. The resulting reason code was reasoncode value.

User responseEnsure that IBM MQ is properly installed andconfigured, and accessible to the user runningMQListener. Consult the IBM MQ documentation formore information, particularly the ApplicationProgramming Reference for more information aboutthe reason code.

Severity8 (Error)

DSNQ022I MQListener failed to disconnectfrom MQ queue manager queuemanager name: reason code =reason code value.

ExplanationMQListener encountered a MQ error error whileattempting to disconnect from MQ queue manager


queue manager name. The resulting reason code wasreason code value.

User responseEnsure that IBM MQ is properly installed and running.Consult the IBM MQ documentation for moreinformation, particularly the Application ProgrammingReference for more information about the reason code.

Severity4 (Warning)

DSNQ030I MQListener encountered a DB2database error attempting to add anew task to the MQListenerconfiguration configuration namein the subsystem subsystem name.The input queue specified in thetask was input queue name and thespecified queue manager wasqueue manager name. Theresulting sqlstate was sqlstatevalue ( sqlcode = sqlcode value ).

ExplanationMQListener encountered a Db2 database error whileattempting to add a new task to the MQListenerconfiguration configuration name in the subsystemsubsystem name. The input queue specified in the taskwas input queue name and the specified queuemanager was queue manager name. The resultingsqlstate was sqlstate value ( sqlcode = sqlcode value ).

User responseConsult MQListener documentation and ensure thatMQListener is properly installed in the specifiedsubsystemand and access to MQListener packagesand configuration tables has been granted to the userrunning MQListener. Ensure that the combination ofconfiguration name, input queue, and queue manageris unique among the MQListener configuration tasks inthe subsystem. Use MQListener "show" command toinspect the configuration.

Severity8 (Error)

DSNQ040I MQListener encountered a DB2database error retrievingconfiguration configuration namefrom subsystem subsystem nameduring operation operation name.The resulting sqlstate was sqlstatevalue ( sqlcode = sqlcode value ).

ExplanationMQListener encountered a Db2 database error whileretrieving configuration configuration name fromsubsystem subsystem name during operationoperation name. The resulting sqlstate was sqlstatevalue ( sqlcode= sqlcode value ).

User responseConsult MQListener documentation and ensure thatMQListener is properly installed in the specifiedsubsystem and access to MQListener packages andconfiguration tables has been granted to the userrunning MQListener.

Severity8 (Error)

DSNQ060I MQListener encountered a DB2database error while removing atask from configurationconfiguration name in subsystemsubsystem name. The input queuespecified was input queue nameand the queue manager specifiedwas queue manager name. Theresulting sqlstate was sqlstatevalue ( sqlcode = sqlcode value ).

ExplanationMQListener encountered a Db2 database error whileremoving a task from configuration configuration namein subsystem subsystem name. The input queue thatwas specified was input queue name, and the queuemanager that was specified was queue manager name.The resulting sqlstate was sqlstate value ( sqlcode =sqlcode value ).

User responseConsult MQListener documentation and ensure thatMQListener is properly installed in the specifiedsubsystem. Also, ensure that access to MQListenerpackages and configuration tables has been granted tothe user who is running MQListener.

Severity8 (Error)

DSNQ061I MQListener attempted to removean unknown task fromconfiguration configuration namein subsystem subsystem name. Theinput queue specified was inputqueue name and the queue

Chapter 12. DSNQ messages 431

manager specified was queuemanager name.

ExplanationMQListener attempted to remove an unknown taskfrom configuration configuration name in subsystemsubsystem name. The input queue that was specifiedwas input queue name and the queue manager thatwas specified was queue manager name.

User responseEnsure that specified parameters are correct, and re-run MQListener. Use MQListener "show" command toinspect the configuration.

Severity0 (Informational)

DSNQ070I MQListener has encountered aDB2 database error preparing torun the stored procedure schemaname. procedure name insubsystem subsystem name:sqlstate = sqlstate value ( sqlcode= sqlcode value ).

ExplanationMQListener has encountered a Db2 database errorwhile preparing to run the stored procedure schemaname. procedure name in subsystem subsystem name.The resulting sqlstate was sqlstate value ( sqlcode =sqlcode value ).

User responseEnsure that MQListener configuration is correctlyspecified and that a stored procedure of the specifiedschema and name exists with a correct signature andis accessible to the user running MQListener.

Severity8 (Error)

DSNQ071I MQListener encountered anunsupported datatype in thesignature of the stored procedureschema name. procedure name inthe subsystem subsystem name:datatype = datatype value.

ExplanationMQListener encountered an unsupported datatype inthe signature of the stored procedure schema name.

procedure name in the subsystem subsystem name.The datatype was datatype value.

User responseConsult the MQListener documentation and ensurethat the stored procedure has the correct datatype.

Severity8 (Error)

DSNQ072I MQListener was unable to start athread running a task specified inthe configuration configurationname by the input queue inputqueue name and queue managerqueue manager name. The ECFerror code was error code value.

ExplanationMQListener was unable to start a thread running a taskthat was specified in the configuration configurationname by the input queue input queue name and queuemanager queue manager name. The ECF error codewas error code value.

User responseEnsure that MQListener configuration is correct,especially the -numInstances parameter, and that theMQListener process has sufficient system resources toexecute the required number of simultaneous tasks.

Severity8 (Error)

DSNQ073I MQListener started a threadrunning the task specified in theconfiguration configuration nameby the input queue input queuename and queue manager queuemanager name.

ExplanationMQListener started a thread running the task that wasspecified in the configuration configuration name bythe input queue input queue name and queue managerqueue manager name.

User responseNone. This is the formal notification of a thread start,expected during startup or restart.



DSNQ074I A thread running the taskspecified in the configurationconfiguration name by the inputqueue input queue name andqueue manager queue managername has exited.

ExplanationA thread running the task specified in the configurationconfiguration name by the input queue input queuename and queue manager queue manager name hasexited.

User responseNone. This is the formal notification of a thread exit,expected during shutdown or restart.


DSNQ075I MQListener encountered a DB2database error while running thestored procedure schema name.procedure name in subsystemsubsystem name during operationoperation name. The resultingsqlstate was sqlstate value( sqlcode = sqlcode value ).

ExplanationMQListener encountered a Db2 database error whilerunning the stored procedure schema name. procedurename in subsystem subsystem name during operationoperation name. The resulting sqlstate was sqlstatevalue ( sqlcode = sqlcode value ).

User responseConsult MQListener documentation and ensure thatMQListener is properly installed in the specifiedsubsystem and access to MQListener packages andconfiguration tables has been granted to the userrunning MQListener. Ensure that the stored procedureexecutes correctly.

Severity8 (Error)

DSNQ080I MQListener received an unknownmessage on admin queue admin

queue name in queue managerqueue manager name: message.

ExplanationMQListener received an unknown message on adminqueue admin queue name in queue manager queuemanager name: message.

User responseEnsure that IBM MQ is correctly installed andconfigured, that MQListener is being run with theproper -adminQMgr and -adminQueue parametervalues, and that the MQListener "admin" command isalso using the proper -adminQMgr and -adminQueueor -adminQueueList parameter values. If used, checkthat the -adminQueueList specifies the proper queuenames. Check that the admin queue is not being usedby another application.

Severity4 (Warning)

DSNQ081I MQListener received a shutdownmessage on admin queue adminqueue name, queue managerqueue manager name.

ExplanationMQListener received a shutdown message on adminqueue admin queue name, queue manager queuemanager name.

User responseNone. This is a formal notification on receiving ashutdown message.


DSNQ082I MQListener received a restartmessage on admin queue adminqueue name, queue managerqueue manager name.

ExplanationMQListener received a restart message on adminqueue admin queue name, queue manager queuemanager name.

Chapter 12. DSNQ messages 433

User responseNone. This is a formal notification on receiving arestart message.


DSNQ084I MQListeners associated withconfiguration --configuration name--, DB2 subsystem --subsystemname-- are shut down.

ExplanationMQListener writes a message to the z/OS console logwhen it is shutdown.

User responseRestart the MQListener.



Chapter 13. DSNR messagesMessage identifiers that begin with DSNR communicate information about the recovery manager andindicate the progress of Db2 through a restart process.

DSNR001I RESTART INITIATED

ExplanationThis message delimits the beginning of the restartprocess within startup. The phases of restart are aboutto begin. These phases are necessary to restore theoperational environment to that which existed at thetime of the previous termination and to perform anyrecovery actions that may be necessary to return Db2-managed resources to a consistent state.

DSNR002I RESTART COMPLETED

ExplanationThis message delimits the completion of the restartprocess within startup.

DSNR003I RESTART...PRIOR CHECKPOINTRBA=xxxxxxxxxxxx

ExplanationThe message indicates the first phase of the restartprocess is in progress and identifies (as'xxxxxxxxxxxx') the log positioning RBA of thecheckpoint from which the restart process will obtainits initial recovery information.

DSNR004I RESTART...UR STATUS COUNTS INCOMMIT=nnnn, INDOUBT=nnnn,INFLIGHT=nnnn, IN ABORT=nnnn,POSTPONED ABORT=nnnn

ExplanationThis message indicates the completion of the firstphase of the restart process. The counts indicate thenumber of units of work whose execution state duringa previous Db2 termination was such that (to ensureDb2 resource consistency) some recovery action mustbe performed during this restart process or (by theuser) upon completion of the restart process. Thecounts of IN COMMIT, INDOUBT, INFLIGHT and INABORT may provide an indication of the time requiredto perform the remaining two phases of restart(forward and backward recovery). The counts ofPOSTPONED ABORT URs may provide an indication ofthe time required to perform -RECOVER POSTPONEDprocessing.

The IN COMMIT count specifies the number that hadstarted but not completed phase 2 of the commitprocess. These must undergo forward recovery tocomplete the commit process.

The INDOUBT count specifies the number that wereinterrupted between phase 1 and phase 2 of thecommit process. These must undergo forwardrecovery to ensure resources modified by them areunavailable until their indoubt status is resolved.

The INFLIGHT count specifies the number that neithercompleted phase 1 of the commit process nor beganthe process of backing out. These must undergobackward recovery to restore resources modified bythem to their previous consistent state.

The IN ABORT count specifies the number that were inthe process of backing out. These must undergobackward recovery to restore resources modified bythem to their previous consistent state.

The POSTPONED ABORT count specifies the numberwhose backout was postponed in an earlier restartprocess and not attended to prior to this restartprocess. These must undergo backward recovery aftercompletion of restart, via the -RECOVER POSTPONEDcommand, to restore resources modified by them totheir previous consistent state.

DSNR005I RESTART...COUNTS AFTERFORWARD RECOVERY INCOMMIT=nnnn, INDOUBT=nnnn

ExplanationThe message indicates the completion of the forwardrecovery restart phase. The counts indicate thenumber of units of work whose recovery actions couldnot be completed during the phase. Typically, those inan IN COMMIT state remain because the recoveryactions of some subcomponents have not beencompleted. Those units of work in an INDOUBT statewill remain until connection is made with thesubsystem that acts as their commit coordinator.

Operator responseNo action is required unless the conditions persistbeyond some installation-defined period of time.Recovery action will be initiated when the resource isbrought online. Indoubt resolution will be initiated aspart of the process of reconnecting the subsystems.


DSNR006I RESTART...COUNTS AFTERBACKWARD RECOVERYINFLIGHT=nnnn, IN ABORT=nnnn,POSTPONED ABORT=nnnn

ExplanationThe message indicates the completion of thebackward recovery restart phase. The counts indicatethe number of units of work whose recovery actionscould not be completed during the phase.

When INFLIGHT or IN ABORT URs do not completebackout during restart, they are converted toPOSTPONED ABORT status, so the INFLIGHT and INABORT counts should be zero. The POSTPONEDABORT count indicates the number of URs for whichbackout work still exists (from this or a previousrestart).

Backout work for the POSTPONED ABORT URs shouldbe completed by the user (by using the RECOVERPOSTPONED command) after Db2 restart hascompleted.

Operator responseNo action is required unless the condition persistsbeyond some installation-defined period of time.Recovery action will be initiated when the resourcecollection is brought online.

Related tasksResolving postponed units of recovery (Db2Administration Guide)Deferring restart processing (Db2Administration Guide)Related reference-RECOVER POSTPONED (Db2) (Db2 Commands)

DSNR007I RESTART...STATUS TABLE

ExplanationThis message precedes a table showing the status ofunits of recovery (URs) after each restart phase. Themessage and the table will accompany the DSNR004I,DSNR005I, or DSNR006I message after each nestedphase. At the end of the current status rebuild phase, itshows the status of any URs that require processing.At the end of the forward recovery and backoutphases,it shows the status of only those URs which neededprocessing but were not processed. The table helps toidentify the URs that were active when Db2 camedown, and to determine the log scope required to bringDb2 up.

The following list describes each column of the table:

TConnection type. The values could be:B

Batch: a batch program or QMF user.I

Internal: a system service being performed onsome user's behalf.

SSubsystem: work that originated from anattached subsystem, either CICS or IMS/VS.

CONIDConnection identifier for related URs. Batchconnections are not related to any otherconnection. Subsystem connections with the sameidentifier indicate URs that originated from thesame subsystem.

CORRIDCorrelation identifier; unique within a subsystemconnection, it relates a UR to a particular CICS orIMS/VS transaction.

AUTHORIZATION IDAuthorization identifier of the user for whom thisUR was created.

PLANName of the plan allocated to the UR.

SRestart status of the UR. When Db2 came down,the UR was in one of these situations:A

INABORT: The UR was in the 'must-complete'phase of abort, and is yet to be completed.

CINCOMMIT: The UR was in the 'must-complete'phase of commit, and is yet to be completed.

DINDOUBT: The UR had completed the firstphase of commit, but Db2 had not received thesecond phase instruction. The UR must beremembered so it can be resolved when theowning subsystem reattaches.

FINFLIGHT: The UR had not completed the firstphase of commit, and will be backed out.

PPOSTPONED ABORT: The UR has not yetcompleted backout. Backout must becompleted outside of Db2 restart by means ofthe -RECOVER POSTPONED command.

URIDUR identifier, the log RBA of the beginning of thisunit of work. It is the earliest RBA required toprocess the UR during Restart.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_resolvepostponedunits.html





DAYThe day the UR was created, in the format 'ddd'. Itis approximately the time of the first SQLstatement of the application or the first SQLstatement following a commit point.

TIMEThe time the UR was created, in the format 'hh mmss '. It is approximately the time of the first SQLstatement of the application or the first SQLstatement following a commit point.

DSNR009I STORAGE IS NOT AVAILABLE FORTHE UR DISPLAY TABLE, THE SIZEREQUESTED = xxxx, STORAGEMANAGER REASON CODE =yyyyyyyy

ExplanationThere was not enough storage available during thecreation of the recoverable UR (RURE) display table(DSNDRUDT).

System actionThe system continues to restart but the RESTART...STATUS TABLE is not displayed.

Operator responseSave the console output and inform the systemprogrammer.

System programmer responseIncrease the region size of the ssnmMSTR addressspace before restarting Db2 again.

Problem determinationThe size requested is approximately 110 bytes foreach unit of recovery (UR). See the messageDSNR004I to determine the total number of URs toprocess. Then get the 00E2xxxx reason code from theDSNR009I header. Use these two numbers todetermine the reason for the shortage.

DSNR010I AN ERROR OCCURRED IN THERURE STATUS TABLE SORT/TRANSLATE MODULE(DSNRUSOR), THE ERRORLOCATION CODE = xxxx

ExplanationThere was an error in processing the RURE displaytable. One of these ERROR LOCATION CODES tellswhat function the module was attempting to perform:

X'0001'Trace entry to the module

X'0002'Sort the recoverable UR display table

X'0003'Translate the recoverable UR table

X'0004'Convert the store clock value for display

X'0005'Trace exit from the module



System programmer responseUse the error code in the message to complete theproblem description.

Problem determinationThe ERROR CODE tells the problem area and should beused in the problem description. A record was addedto the SYS1.LOGREC that contains the PSW andmodule at the time of the error. This error indicates anapplication program check of some type.

DSNR011I AN ERROR OCCURRED IN THERURE STATUS TABLE DISPLAYMODULE (DSNRUDIS), THE ERRORLOCATION CODE = xxxx

ExplanationThere was an error in processing the RURE displaytable. One of these ERROR LOCATION CODES tellswhat function the module was attempting to perform:X'0001'

Trace entry to the moduleX'0002'

Build header for the display tableX'0003'

Build entries for the display tableX'0004'

Call DSNRWTO to display the tableX'0005'

Trace exit from the module

Chapter 13. DSNR messages 437

X'0006'Get message text



System programmer responseUse the error code in the message to complete theproblem description.

Problem determinationThe ERROR CODE describes the problem area andshould be used in the problem description. A recordwas added to the SYS1.LOGREC containing the valueDSNRUDIS, and the PSW and CSECT at the time of theerror. This error indicates an application programcheck of some type.

Error codes other than X'0006' indicate an applicationprogram check of some type. Code X'0006' indicatesan error attempting to locate the table text. The traceentry for DSNRUDIS contains the return and reasoncodes from the Get Text request. That informationshould be used to complete the problem description.

DSNR014I EXCLUDED RURE TABLE

ExplanationThis message contains a list of RUREs which are beingbypassed because of the conditional restart. Eitherthey were to be processed in a phase that wasbypassed or they were outside the log range.

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 onsome user's behalf.

SSubsystem: work that originated from anattached subsystem, either CICS or IMS/VS.

CONIDConnection identifier for related URs. Batchconnections are not related to any other

connection. Subsystem connections with the sameidentifier indicate URs that originated from thesame subsystem.

CORRIDCorrelation identifier; unique within a subsystemconnection, it relates a UR to a particular CICS orIMS/VS transaction.

AUTHORIZATION IDAuthorization identifier of the user for whom thisUR was created.

PLANName of the plan allocated to the UR.

SRestart status of the UR. When Db2 came down,the UR was in one of these situations:A

INABORT: The UR was in the 'must-complete'phase of abort, and is yet to be completed.

CINCOMMIT: The UR was in the 'must-complete'phase of commit, and is yet to be completed.

DINDOUBT: The UR had completed the firstphase of commit, but Db2 had not received thesecond phase instruction. The UR must beremembered so it can be resolved when theowning subsystem reattaches.

FINFLIGHT: The UR had not completed the firstphase of commit, and will be backed out.

PPOSTPONED ABORT: The UR has not yetcompleted backout. Backout must becompleted outside of Db2 restart by means ofthe -RECOVER POSTPONED command.

URIDUR identifier, the log RBA of the beginning of thisunit of work. It is the earliest RBA required toprocess the UR during Restart.

DAYThe day the UR was created, in the format 'ddd'. Itis approximately the time of the first SQLstatement of the application or the first SQLstatement following a commit point.

TIMEThe time the UR was created, in the format 'hh mmss'. It is approximately the time of the first SQLstatement of the application or the first SQLstatement following a commit point.

System actionRestart continues.


DSNR015I THE CHKPTRBA xxxxxxxxxxxxSPECIFIED IN THE CRCR ISINVALID

ExplanationThe checkpoint RBA specified in the conditional restartcontrol record (CRCR) is either not available or is not abegin checkpoint record.

System actionRestart is abended with reason code '00D99001'.

Operator responseInform the system programmer.

System programmer responseBy specifying the STARTRBA and/or ENDRBA on theCRESTART control statement, change log inventory(DSNJU003) utility selects an appropriate RBA.

Problem determinationPrint the complete checkpoint records queue by usingthe print log map (DSNJU004) utility. Select acheckpoint RBA from this queue or let the change loginventory (DSNJU003) utility make the selection.

DSNR016I STARTRBA xxxxxxxxxxxxVALIDATION FAILED

ExplanationA scan from the STARTRBA failed to find a completelog record. Either the entire log was scanned and nocomplete record was found, or the log manager foundan invalid log record. The log manager sends the errormessages to the console indicating a bad log record.

System actionRestart abends.

Operator responseRecord the log manager message numbers and informthe system programmer.

System programmer responseUse DSN1LOGP to determine a STARTRBA to use forrestart. The recovery manager uses the STARTRBA asa starting point for its search of the beginning of a validlog record.

DSNR017I RESTART IS BEING TERMINATEDBECAUSE OF CSRONLYSPECIFICATION IN CRCR

ExplanationThe restart procedure only completed the first phaseof startup. The status displayed during this partialrestart can be used to build the conditional restartcontrol record (CRCR).

System actionRestart is abended.

System programmer responseTo prevent the restart control record from beingreused during the next restart attempt, the currentrestart control record must be canceled. Use thechange log inventory (DSNJU003) CRESTART CANCELoption, or create a new restart control record. Thenewly created restart control record will automaticallycancel the previous record.

DSNR018I csect-name RESTART...BACKWARDRECOVERY PROCESSED FROMRBA ffffffffffff TO RBA tttttttttttt

ExplanationThis message indicates the range of log processedduring the backward phase of RESTART whenpostponed backout processing has been requested.Processing began with the LR of RBA ffffffffffff andproceeded backwards to the LR of RBA tttttttttttt.

System actionThis message is followed by messages DSNR006I andDSNR007I. The former tells how many URs had somebackout work postponed. The latter, identifies thepostponed abort URs. The amount of log that need tobe processed to complete backout processing for thepostponed abort URs can be gauged by comparing theRBA reached during RESTART's backward processing(RBA tttttttttttt), and the URIDs of the postponed abortURs.

DSNR020I csect-name START MEMBERmember, OR REPLY 'NO' OR'QUIESCED'

ExplanationDuring a group restart, the group member issuing thismessage attempted to access the BSDS for membermember, and either was not able to access the BSDS,or discovered that the BSDS was modified by the


change log inventory (DSNJU003) utility since thatmember was last started. In either case, this Db2 isnot able to perform peer restart for member member.

For group restart to continue, the identified membermust be started.

If it is not possible to start the other member and youwant to terminate this group restart, you can reply 'NO'to this message. Replying 'NO' to this message causesthis Db2 to terminate with a reason code of00D900E1. You then have to reply 'NO' to thismessage for all remaining members participating inthis group restart.

If you are sure that the identified member wasquiesced the last time it was started, that is, it wasstopped with a -STOP DB2 MODE(QUIESCE) commandand it stopped with no indoubt units of recovery andno distributed resynchronization responsibility, thenyou can reply 'QUIESCED' to this message. Replying'QUIESCED' to this message causes messageDSNR030I to be issued as a reminder that grouprestart will continue without using the log from theidentified member.

System actionThis group member waits for the identified member tobe started or for a valid reply to this message.

• If the identified member is started, group restartcontinues.

• If the reply is 'NO', this Db2 terminates with a reasoncode of 00D900E1.

• If the reply is 'QUIESCED', group restart continueswithout using the log from the identified member.

DSNR021I csect-name DB2 SUBSYSTEMMUST PERFORM GROUP RESTARTFOR PEER MEMBERS

ExplanationThis Db2 subsystem must perform the group restartphase to recover either the shared communicationsarea (SCA) or the retained locks for nonstartingmembers in the data sharing group.

This message marks the beginning of group restartprocessing for peer members. Messages DSNR023Iand DSNR024I or messages DSNR025I and DSNR026Iare issued for each peer that is processed by this Db2subsystem. Message DSNR022I marks the end ofgroup restart processing for peer members.

This message is issued before this Db2 member entersthe group restart process. The group restart process issynchronized among all group members that arestarting and therefore participating in this group

restart. After this Db2 member synchronizes withother members, it is possible that no peer processingwill be necessary; in that case message DSNR022Iimmediately follows this message.

If it is necessary to recover both the SCA and retainedlocks, this message is issued twice; once for SCArecovery and again for the recovery of the retainedlocks.

System actionThe subsystem begins group restart processing.

DSNR022I csect-name DB2 SUBSYSTEM HASCOMPLETED GROUP RESTART FORPEER MEMBERS

ExplanationThis Db2 subsystem, which previously issued messageDSNR021I, completed the group restart phase torecover the shared communications area (SCA) orretained locks for nonstarting Db2 members in thedata sharing group.

System actionThe subsystem continues with the next restart phaseof its own subsystem.

DSNR023I csect-name GROUP RESTARTINITIATED TO RECOVER THE SCAFOR GROUP MEMBER membname

ExplanationThe Db2 subsystem that issued this message isperforming the group restart phase to recover theshared communications area (SCA) for nonstartingmember membname of the data sharing group.

This message is followed by message DSNR024I afterthe group restart phase to recover the SCA for theidentified member is complete.

System actionThe subsystem continues the group restart process.

DSNR024I csect-name GROUP RESTARTCOMPLETED TO RECOVER THESCA FOR GROUP MEMBERmembname

ExplanationThe Db2 subsystem that issued this messagecompleted the group restart phase to recover the


shared communications area (SCA) for membermembname of the data sharing group.

This message is issued only if messages DSNR021Iand DSNR023I were issued.


DSNR025I csect-name GROUP RESTARTINITIATED TO RECOVERRETAINED LOCKS FOR GROUPMEMBER membname

ExplanationThe Db2 subsystem that issued this message isperforming the group restart phase to recover theretained locks for nonstarting member membname ofthe data sharing group.

This message is followed by message DSNR026I afterthe group restart phase to recover the retained locksfor the identified member is complete.


User responseRestart the failed member to release the retainedlocks.

DSNR026I csect-name GROUP RESTARTCOMPLETED TO RECOVERRETAINED LOCKS FOR GROUPMEMBER membname

ExplanationThe Db2 subsystem that issued this messagecompleted the group restart phase to recover theretained locks for member membname of the datasharing group.

This message is issued only if messages DSNR021Iand DSNR025I were issued.


DSNR030I csect-name WILL CONTINUEWITHOUT THE member MEMBER'SLOG, REPLY 'YES' OR 'NO'

ExplanationThe reply to message DSNR020I was 'QUIESCED'. Thismessage is issued as a reminder that group restart willcontinue without using the log from the identifiedmember.

If you are sure that the identified member wasquiesced the last time it was started, that is, it wasstopped with a -STOP DB2 MODE(QUIESCE) commandand it stopped with no indoubt units of recovery andno distributed resynchronization responsibility, thenreply 'YES'; otherwise, reply 'NO'.

System actionThis group member waits for a valid reply to thismessage.

• If the reply is 'YES', group restart continues withoutusing the log from the identified member.

• If the reply is 'NO', message DSNR020I is reissued toallow you to enter a different response.

DSNR031I csect-name PROCESSING LOGRECORD AT RBA rba1 TO RBA rba2

ExplanationThis message is produced periodically during theforward and backward processing phases of restart.The RBA values in this message can be used tomonitor the progress of the phases of restart.

Forward processing occurs between messagesDSNR004I and DSNR005I. During forward processing,the log is read in a forward direction.

Backward processing occurs between messagesDSNR005I and DSNR006I. During backwardprocessing, the log is read in a backward direction andreading stops at the RBA that matches the URID of theoldest inflight or in-abort UR.


rba1The RBA of the log record that is currently beingprocessed.

rba2The RBA of the last log record that is read in thisphase of restart.

If rba1 is not progressing, restart might be suspended.Messages DSNR055I through DSN058I mightaccompany this message and provide additionaldiagnostic information to help identify the cause of thesuspension.


System actionDb2 restart continues.

Operator responseIf rba1 is not progressing, notify the systemprogrammer.

System programmer responseIf rba1 is not progressing, take one of the followingactions:

• If messages DSNR055I through DSNR058I indicatethe reason for the suspension, follow theinstructions for those messages to resolve therestart suspension.

• If messages DSNR055I through DSNR058I are notdisplayed or do not provide enough information,request SVC dumps of the Db2 and IRLM addressspaces for problem determination. For data sharing,request dumps from all members of the data sharinggroup.


Related tasksRequesting Db2 SVC dumps (Collecting data)Related informationDSNR004IRESTART...UR STATUS COUNTS INCOMMIT=nnnn, INDOUBT=nnnn,INFLIGHT=nnnn, IN ABORT=nnnn, POSTPONEDABORT=nnnnDSNR005IRESTART...COUNTS AFTER FORWARDRECOVERY IN COMMIT=nnnn, INDOUBT=nnnnDSNR006IRESTART...COUNTS AFTER BACKWARDRECOVERY INFLIGHT=nnnn, IN ABORT=nnnn,POSTPONED ABORT=nnnnDSNR055Icsect-name RESTART SUSPENDED SINCE timeIN module offset maint-lvlDSNR056Icsect-name RESTART SUSPENDED ON IRLMREQUEST. ONE HOLDER OF RESOURCE IS ss-name. SERVICE INFO: IRLM FUNC func-cd,RESOURCE res-name.DSNR057Icsect-name RESOURCE INFORMATION: DBIDX'dbid', PSID X'psid', PART X'part#'DSNR058I

csect-name ACCESSING ARCHIVE LOG data-set-name

DSNR034E csect-name THERE CANNOT BEMORE THAN TWO RELEASELEVELS OF DB2 RUNNING IN THEGROUP

ExplanationYou attempted to start a Db2 that was at a releaselevel that cannot coexist in the data sharing group.There are already two different releases of Db2currently running in the data sharing group.

System actionDb2 terminates.

System programmer responseIf you are sure that the startup procedure is pointing tothe correct set of load libraries, you must stop any Db2subsystems that cannot coexist with the one you areattempting to start.

Related conceptsRelease coexistence in Db2 data sharing (Db2Installation and Migration)Recommendation for group restart incoexistence (Db2 Installation and Migration)Related tasksMigrating an existing data sharing group to Db211 conversion mode (Db2 Installation andMigration)Preparing for Db2 11 migration in Db2 datasharing (Db2 Installation and Migration)

DSNR035I csect-name WARNING -UNCOMMITTED UR AFTER numberCHECKPOINTS - CORRELATIONNAME = correlation-nameCONNECTION ID = connection-idLUWID = logical-unit-of-work-id=token PLAN NAME = plan-nameAUTHID = authorization-id ENDUSER ID = user-id TRANSACTIONNAME = transaction-nameWORKSTATION NAME =workstation-name

ExplanationThis message indicates that during checkpointprocessing, Db2 encountered an uncommitted unit ofrecovery (UR) that has an inflight or indoubt status.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_requestingsvcdumps.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsharerelcoexist.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsharerelcoexist.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_recforgrouprestart.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_recforgrouprestart.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_migrateexistdsgroup.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_prepdsharegrpmigr.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_prepdsharegrpmigr.html


numberThe cumulative number of checkpoints that weretaken since the beginning of the UR.

correlation nameThe correlation name for the thread that isassociated with the UR.

connection-idThe connection ID for the thread that is associatedwith the UR.

logical-unit-of-work-idThe logical unit of work ID for the thread that isassociated with the UR. An asterisk (*) denotesthat the thread originated at the local site.



If the UR is inflight, token refers to the thread inthe report from the DISPLAY THREAD commandwith the TYPE(ACTIVE) option.

If the UR is indoubt, token might not refer to thethread in the report from the DISPLAY THREADcommand with the TYPE(INDOUBT) option.However, in this case, you can use the logical unitof work ID to determine the correct association.

plan-nameThe plan for the thread that is associated with theUR.

authorization-idThe authorization ID for the thread that isassociated with the UR.

user-idThe user ID that is associated with the UR, if thethread was created with client user information.Otherwise, an asterisk (*).

transaction-nameThe transaction that is associated with the UR, ifthe thread was created with client userinformation. Otherwise, an asterisk (*).

workstation-nameThe workstation host name that is associated withthe UR, if the thread was created with client userinformation. Otherwise, an asterisk (*).

System actionProcessing continues. If statistics class 3 is turned on,IFCID 0313 is written.

System programmer responseYou can see the UR in the DISPLAY THREADTYPE(ACTIVE) report or the DISPLAY THREADTYPE(INDOUBT) report. Depending on which report isrelevant, take one of the following actions:

If the UR is in the DISPLAY THREAD TYPE(ACTIVE)report:

Consult with the application programmer todetermine whether this UR is problematic.

If the problematic UR is caused by an applicationprogram, you can use the CANCEL THREADcommand to roll back the UR, if necessary. Input tothe command can be the logical-unit-of-work-idvalue or the token value. The amount of timerequired for the backout process depends on theamount of work performed by the UR.

For more information about problems caused byuncommitted URs, see the information aboutprogramming for concurrency.

If the UR is in the DISPLAY THREADTYPE(INDOUBT) report:

The UR is typically resolved automatically in areasonable amount of time. However, in caseswhere the UR is not resolved, consider using theRECOVER INDOUBT command to provide a commitor abort decision. Input to the command can bethe logical-unit-of-work-id value, the token value,or any other appropriate value that is provided inthe DISPLAY THREAD TYPE(INDOUBT) report. Theamount of time required for the backout processdepends on the amount of work performed by theUR.

Programmer responseEnsure that the application commits frequentlyenough, or consult with your Db2 administrator aboutdecreasing the frequency of the check foruncommitted URs. Use the URCHKTH subsystemparameter.

Related tasksDisplaying threads by LUWID (Db2Administration Guide)Programming for concurrency (Db2Performance)Related referenceUR CHECK FREQ field (URCHKTH subsystemparameter) (Db2 Installation and Migration)






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_urchkth.html


DSNR036I csect-name UNRESOLVED URENCOUNTERED DURINGCHECKPOINT - CORRELATIONNAME = correlation-nameCONNECTION ID = connection-idLUWID = logical-unit-of-work-idPLAN NAME = plan-name AUTHID= authorization-id

ExplanationDb2 detected an INDOUBT unit of recovery (UR) duringa checkpoint. Either an INDOUBT UR or POSTPONEDABORT UR exists.


correlation nameThe correlation name that is associated with theUR.

connection-idThe connection ID that is associated with the UR.

logical-unit-of-work-idThe logical unit of work ID. An asterisk (*) denotesthat the thread originated at the local site.


plan-nameThe plan that is associated with the UR.

authorization-idThe authorization ID that is associated with theUR.

System actionProcessing continues. If statistics class 3 is turned on,IFCID 0313 is written.

System programmer responseConsult with the application programmer to determineif this UR is problematic.

Related tasksDisplaying threads by LUWID (Db2Administration Guide)Resolving indoubt units of recovery (Db2Administration Guide)

Related referenceUR CHECK FREQ field (URCHKTH subsystemparameter) (Db2 Installation and Migration)

DSNR037I csect-name WARNING - THETCP/IP DRDA PORT NUMBER ISCHANGED FROM port-1 TO port-2

ExplanationThe TCP/IP DRDA port number specified in the Db2BSDS is different from the value used the last time amember of the Db2 data sharing group started. Allmembers of a Db2 data sharing group must use thesame TCP/IP DRDA port number.csect-name


port-1The TCP/IP DRDA port number that was obtainedfrom the coupling facility during Db2 startup. Thisvalue is the TCP/IP DRDA port number that wasused the last time a member of the data sharinggroup was started.

port-2The TCP/IP DRDA port number that was obtainedfrom the Db2 BSDS during Db2 startup.

System actionDb2 accepts the new TCP/IP DRDA port number, andDb2 startup continues.


System programmer responseIf the TCP/IP DRDA port number was changedinadvertently, stop Db2 immediately. Use the changelog inventory utility (DSNJU003) to correct the PORTvalue, and restart Db2.

If this message reflects a change that you want tomake to the Db2 DRDA port number, no action isrequired. The DRDA port number stored in thecoupling facility is updated, and this new port numberwill be used when Db2 validates each member's DRDAport number.

DSNR038I csect-name WARNING - THETCP/IP RESYNCHRONIZATIONPORT NUMBER IS CHANGED FROMport_1 TO port_2








ExplanationThe TCP/IP resynchronization port number obtainedfrom the DDF record of the BSDS is different than thevalue specified the last time Db2 started.

Changing the TCP/IP resynchronization port numbercan cause problems during distributed 2-phasecommit processing. The remote DRDA partners recordDb2 resynchronization port number in their recoverylogs. The resynchronization port number is used toreconnect to the appropriate Db2 member whencommunication failures occur during 2-phase commitprocessing. If a Db2 member changes itsresynchronization port number, the remote DRDApartners may be unable to resolve indoubt units ofwork.port_1

The TCP/IP resynchronization port number thatwas obtained from the Db2 BSDS during Db2startup.

port_2The TCP/IP resynchronization port number thatwas obtained from the coupling facility during Db2startup. This is the TCP/IP resynchronization portnumber that was used the last time this memberwas started.

System actionDb2 accepts the new TCP/IP resynchronization portnumber, and Db2 startup continues.


System programmer responseIf the Db2 resynchronization port number waschanged inadvertently, stop Db2 immediately. Use thechange log inventory utility (DSNJU003) to correct theRESPORT value, and restart Db2.

If this message reflects a change that you want tomake to the Db2 resynchronization port number, noaction is required. The resynchronization port numberstored in the coupling facility for this member isupdated, and this new port number will be used whenDb2 validates the resynchronization port number forother Db2 members.

DSNR039I csect-name WARNING - TCP/IPRESYNCHRONIZATION PORTNUMBER port_1 IS THE SAME ASMEMBER member_name

ExplanationThe TCP/IP resynchronization port of the starting Db2is the same as the member indicated bymember_name.port_1

The TCP/IP resynchronization port number thatwas obtained from the Db2 BSDS during Db2startup.

member_nameThe member name of the Db2 data sharingmember that used the same resynchronizationport number.

System actionThe TCP/IP port number specified in the BSDS isaccepted, and Db2 startup continues.


System programmer responseEach member of the Db2 data sharing group shouldhave a unique TCP/IP resynchronization port number.Use the change log inventory utility (DSNJU003) tospecify a unique RESPORT value for this Db2 memberand the Db2 member identified by member_name.

DSNR040I csect-name TRACKER RESTARTENDLRSN lrsn DOES NOT MATCHENDLRSN lrsn ASSOCIATED WITHTHE DATA SHARING GROUP

ExplanationIn a data sharing environment, a TRKRSITE Db2 willnot restart if it detects inconsistencies in the reportedvalues for ENDLRSN. The ENDLRSN specified on theConditional Restart Control Record does not match theENDLRSN in the system communications area (SCA)structure for the data sharing group.


Operator responseCollect the SYS1.LOGREC and SVC dump, and contactthe system programmer.

System programmer responseIf the ENDLRSN value for this member is incorrect,take the following actions:


• Restore the BSDS and Logs for his Tracker Db2 fromthe primary Db2

• Ensure the Conditional Restart Control Record iscorrect

• Restart Db2

If the ENDLRSN value in the SCA is incorrect, deletethe SCA structure and restart all members of theTRKRSITE data sharing group with the sameENDLRSN.

DSNR042I csect-name WARNING - URROLLBACK HAS BEEN CANCELEDAND IS INCOMPLETE FORCORRELATION NAME = corridCONNECTION ID = connid AUTHID= authid PLAN NAME = plan-nameURID = urid

ExplanationDb2 issues this message when rollback for theindicated thread has been canceled by either theCANCEL THREAD NOBACKOUT command or theRECOVER POSTPONED CANCEL command.

System actionRollback processing for the thread stops and the unitof recovery is logged as canceled and complete.

User responseExamine the console for messages indicating whatobjects are being marked as REFP,RECP; those objectswill need to be recovered.

DSNR043E csect-name DB2 IS STARTINGWITH AN UNSUPPORTED CODELEVEL. CURRENT LEVEL: current-code-level VALID LEVEL(S): valid-code-levels

ExplanationThe Db2 that is starting is not at the proper code level.Some required maintenance, such as a fallback orcoexistence SPE, has not been applied. The levelinformation is different for each SPE level and eachrelease. This information is for the use of your IBMservice representative.

This message can occur in the following situations:

• The Db2 that is starting has completed a fallbackfrom a later release and does not have the properfallback SPE applied.

• The Db2 that is starting does not have the propercoexistence SPE to start in a data sharing group,which is at a later release level.

• The Db2 that is starting is not at a release level thatsupports coexistence with the data sharing group.

System actionDb2 terminates with reason code 00D900FA.


System programmer responseCheck the Db2 Program Directory and PreventiveService Planning updates (PSP) to determine what SPEyou need.

Verify that:

• Coexistence is supported between the releases youare trying to run.

• The Db2 startup procedure points to the correct setof load libraries.

• The correct SPE has been applied.




• Contents of the BSDS (both copies if dual BSDS inuse) obtained by using the Db2 print log map(DSNJU004) utility.

• Unformatted DSN1PRNT output of theDSNDB01.DBD01 page set. Locate the inconsistentDBD in the DSNDB01.DBD01 page set by using themethod described in Db2 Diagnosis Guide andReference.

DSNR044E csect-name MEMBER member-name IS STARTED AT A LEVEL OFCODE started-code-level WHICH ISNOT COMPATIBLE WITH THESTARTING MEMBER. VALIDLEVEL(S) valid-code-levels

ExplanationThe code levels are not compatible between the Db2member that has already started and the Db2 member


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_digref.html




that is starting. You need to apply the correct SPE tothe Db2 member that is at the earlier level.

The level information is different for each SPE leveland each release. This information is for the use ofyour IBM service representative.

This message occurs when a starting Db2 member isat a later release level that cannot coexist with anexisting Db2 member.

System actionAfter detecting the first member with which it cannotcoexist, Db2 terminates with reason code 00D900FA.


System programmer responseCheck the Program Directory and Preventive ServicePlanning updates (PSP) to ensure that all activemembers in the group have the proper SPE applied.

Verify that:

• Coexistence is supported between the releases youare trying to run.

• The Db2 startup procedure points to the correct setof load libraries.

• The correct SPE has been applied.





• Unformatted DSN1PRNT output of theDSNDB01.DBD01 page set. Locate the inconsistentDBD in the DSNDB01.DBD01 page set by using themethod described in Db2 Diagnosis Guide andReference.

DSNR045I csect-name DB2 SUBSYSTEM ISSTARTING AND IT WAS NOTSTARTED IN A PREVIOUSRELEASE WITH THE FALLBACKSPE APPLIED. FALLBACK SPEAPAR: apar-number NEW RELEASE

LEVEL: release KNOWN LEVEL(S):level

ExplanationDb2 was not started with the FALLBACK SPE activebefore an attempt was made to start Db2 in a newrelease. The FALLBACK SPE must be applied, and thesystem must be started before Db2 can be started in anew release.

release levelThe release and level are different for eachrelease, and are for the use of the IBM servicerepresentative.

apar-numberThe apar-number is the FALLBACK SPE that ismissing.

System actionDb2 terminates with reason code 00D96001.

User responseEnsure that the FALLBACK SPE is applied, and Db2 isstarted before starting Db2 in a new release.

DSNR046I csect-name INCOMPLETE UNITSOF RECOVERY EXIST FOR subsys

ExplanationThis message is issued during Db2 shutdown if anyincomplete units of recovery exist for the referencedmember of a data sharing group. The messageindicates that retained locks will be held by subsystemsubsys.

System actionDb2 shutdown continues normally.

User responseRestart Db2 and resolve the incomplete units ofrecovery to release the retained locks held bysubsystem subsys.

DSNR047I csect-name POSTPONED ABORTBACKOUT PROCESSING LOGRECORD AT RBA rba1 TO RBA rba2

ExplanationThis message is produced periodically during thebackout processing of postponed abort units ofrecovery, initiated by the -RECOVER POSTPONED






command. The RBAs in this message can be used tomonitor the backout progress.

During the backout process, Db2 reads the log in abackward direction and stops reading the log at theRBA matching the URID of the oldest postponed-abortUR rba2. rba1 is the RBA of the log record currentlybeing processed.


System programmer responseThis is an information-only message. If the messagecontinues to be issued and rba1 remains the same,make sure there are no outstanding archive tapemounts that may be delaying the log read process.Otherwise, obtain a dump of the Db2 address spacesfor problem determination.

The -DISPLAY THREAD TYPE(POSTPONED) commandcan be issued to display information about thepostponed abort units of recovery. It is also possible tostop the backout process with the -RECOVERPOSTPONED CANCEL command, but this will leaveobjects in an inconsistent state.

Related reference-RECOVER POSTPONED (Db2) (Db2 Commands)-DISPLAY THREAD (Db2) (Db2 Commands)

DSNR048I csect-name UR BACKOUTPROCESSING LOG RECORD ATRBA rba1 TO RBA rba2 FORCORRELATION NAME =correlation-name CONNECTION ID= connection-id LUWID = logical-unit-of-work-ID=token PLAN NAME= plan-name AUTHID =authorization-ID END USER ID =user-ID TRANSACTION NAME =transaction-name WORKSTATIONNAME = workstation-name

ExplanationThis message is produced periodically during thebackout process of an in-abort unit of recovery. TheRBAs in this message can be used to monitor thebackout progress. Together, CORRELATION NAME,CONNECTION ID, and LUWID identify a threadassociated with the UR. If the LUWID is '*', the threadoriginated at this site. token is a unique token numberassociated with the LUWID. PLAN NAME and AUTHIDfurther identify the thread associated with the UR. Ifthe thread was created with client user information,the user's USERID, TRANSACTION NAME, and

WORKSTATION NAME are displayed. Otherwise, thesefields contain an '*'.

During the backout process, Db2 reads the log in abackward direction and stops reading the log at theRBA matching the URID of the in-abort UR rba2. rba1is the RBA of the log record currently being processed.


System programmer responseThis is an information-only message. If the messagecontinues to be issued and rba1 remains the same,make sure there are no outstanding archive tapemounts that might be delaying the log read process.Otherwise, obtain a dump of the Db2 address spacesfor problem determination.

It might be possible to stop the backout process withthe NOBACKOUT option of the -CANCEL THREADcommand, but this leaves objects in an inconsistentstate.

Related conceptsHow Db2 rolls back work (Db2 AdministrationGuide)Related reference-CANCEL THREAD (Db2) (Db2 Commands)

DSNR050I csect-name DB2 STARTED INSYSTEM RECOVER PENDINGMODE

ExplanationDb2 has started in System Recover Pending mode inpreparation for the RESTORE SYSTEM utility. Nodatabase update activity is allowed, and DB2 is inrestricted access mode.



DSNR051I csect-name SYSPITR RESTARTENDLRSN lrsn DOES NOT MATCHENDLRSN lrsn ASSOCIATED WITHTHE DATA SHARING GROUP

ExplanationFor a System Level Recovery restart, all members ofthe data sharing group must truncate their logs with




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_howrollbackwork.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_howrollbackwork.html


the same LRSN value that was specified in theSYSPITR conditional restart parameter.


Operator responseCollect the SYS1.LOGREC and SVC dump, and contactthe system programmer.

System programmer responseEnsure that the conditional restart control record iscorrect, and then restart Db2. You can run the PrintLog Map utility (DSNJU004) to examine the currentconditional restart record.

DSNR052I csect-name DB2 MEMBER TOREMAIN ACTIVE IN LIGHT MODETO RESOLVE INDOUBT UNITS OFRECOVERY

ExplanationThis message is issued at the end of restart when theDb2 member has been restarted with the LIGHT(YES)parameter and there are indoubt units of recovery(URs).

System actionThe Db2 member remains up and running in lightmode. This Db2 member will only allow connectionsfor the purpose of resolving the indoubt URs. Also,certain commands are allowed. Any attempt toconnect to this Db2 to submit new SQL work will bedisallowed with reason code 00F300A2.

User responseEnsure that the appropriate commit coordinators arestarted so that they can resync with the Db2 memberto resolve the indoubts. Alternatively the -RECOVERINDOUBT command can be used to manually resolvethe indoubts.

DSNR053I csect-name ALL INDOUBT UNITSOF RECOVERY HAVE BEENRESOLVED. LIGHT MODE DB2NORMAL TERMINATION TOFOLLOW

ExplanationThis message is issued after all indoubt units ofrecovery are resolved for this Db2 member, which wasrestarted with the LIGHT(YES) parameter.


System actionDb2 subsystem shutdown is initiated.


Related conceptsRestart light (Db2 Data Sharing Planning andAdministration)

DSNR054I RESTART...BEGIN SCAN FORCHECKPOINT

ExplanationDb2 must scan the log backwards to locate the priorcheckpoint.

System actionAfter the prior checkpoint is located on the log, restartcontinues.

DSNR055I csect-name RESTART SUSPENDEDSINCE time IN module offsetmaint-lvl

ExplanationThis message is produced periodically during therecovery phase of a restart if Db2 detects that therestart processor has remained suspended across atwo minute interval. This message provides the timethat the restart processor has suspended, and, themodule, offset, and maintenance level for the suspendrequest.



System programmer responseIf the message repeats every two minutes and Db2restart does not appear to be progressing, look foradditional messages that could indicate the reason forthe restart stall. If no other messages are found,request SVC dumps of the Db2 and IRLM addressspaces for problem determination. For data sharing,




request dumps from all members of the data sharinggroup.

DSNR056I csect-name RESTART SUSPENDEDON IRLM REQUEST. ONE HOLDEROF RESOURCE IS ss-name.SERVICE INFO: IRLM FUNC func-cd, RESOURCE res-name.

ExplanationThis message is produced periodically during therecovery phase of restart if Db2 detects that therestart processor has remained suspended across atwo minute interval on an IRLM request. If Db2 issuspended for an IRLM lock in a data sharingenvironment, Db2 queries IRLM to determine whatDb2 subsystem holds the lock. If successful, ss-namecontains the Db2 subsystem name. Otherwise, ss-name contains a series of eight asterisks ('********').The function code and resource name for the IRLMrequest is also provided for serviceability.



System programmer responseIf the message repeats every two minutes and Db2restart does not appear to be progressing, the Db2subsystem displayed in the message needs to berecycled to allow this subsystem to restart. If theobject identified by the message is recognized thenconsider issuing a -STOP DATABASE followed by a -START DATABASE command to attempt to free theresource. If the stop and start of the object does notresolve the issue then proceed to recycle the Db2subsystem identified by the message. Request SVCdumps of the Db2 and IRLM address spaces forproblem determination before any STOP/STARTdatabase command or recycling any of the Db2subsystems. For data sharing, request dumps from allmembers of the data sharing group.

DSNR057I csect-name RESOURCEINFORMATION: DBID X'dbid', PSIDX'psid', PART X'part#'

ExplanationThis message is produced periodically during therecovery phase of restart if Db2 detects that therestart processor has remained suspended across atwo minute interval on an IRLM request. If Db2 is

suspended for an IRLM lock in a data sharingenvironment, Db2 queries IRLM to determine whatDb2 subsystem holds the lock. This message indicatesthat the locked resource is a type which is held on adatabase object. The dbid contains the DBID and thepsid contains the PSID in the case of a table space orISOBID in the case of an index space. If the object is apartition of a partitioned pageset, then the part#contains the partition number, otherwise it is zero.



System programmer responseIf the message repeats every two minutes and Db2restart does not appear to be progressing, then anagent running on the Db2 subsystem identified inmessage DSNR056I could be holding on to a lock foran extended period of time, that is associated with theDBID, PSID, PART identified in this message. Youmight be able to use the database object identificationinformation in this message to identify the specificobject which is encountering the problem. One way tocheck what object is encountering the problem is toquery the Db2 catalog to find the database name andpageset name, and then to use the DISPLAYDATABASE CLAIMERS or DISPLAY DATABASE LOCKScommands to identify the agent that is holding thelock. If an agent can be identified, you can cancel theagent to release the lock.

DSNR058I csect-name ACCESSING ARCHIVELOG data-set-name

ExplanationThis message is produced periodically during therecovery phase of restart if Db2 detects that therestart processor has remained suspended across atwo minute interval attempting to access an archivelog data set. The data-set-name contains the data setname of the archive log that Db2 is accessing.




System programmer responseLook for and resolve any outstanding archive log tapemounts or HSM recall requests that could be causingDb2 restart to stall. If this does not resolve theproblem, request SVC dumps of the Db2 and IRLMaddress spaces for problem determination.

DSNR059I csect-name GROUP INFORMATIONIN THE SCA IS NOT CONSISTENTWITH A SYSPITR RESTART

ExplanationGroup information in the shared communication area(SCA) indicates that the current SYSPITR restart isinvalid. All active members of the data sharing groupmust restart with the same SYSPITR conditionalrestart value.



System programmer responseMake sure that all data sharing structures in thecoupling facility have been deleted before the firstSYSPITR restart, and that all active members havebeen restarted with the same SYSPITR conditionalrestart value.

DSNR060I csect-name THIS DB2 SUBSYSTEMIS MARKED AS DEACTIVATED ANDCANNOT BE STARTED.

ExplanationAn attempt was made to start a Db2 subsystem, butthe Db2 subsystem that issued the message cannot bestarted because its BSDS indicates that it has beendeactivated.


System actionAn SVC dump is generated for abend 04E with reasoncode 00D10130. The restart is terminated.

System programmer responseMessage DSNR060I usually indicates that a Db2subsystem which has been deactivated was startedmistakenly. If the Db2 subsystem should not havebeen deactivated, use the change log inventory utility(DSNJU003) to restore the member.


• The SVC dump• The syslog and LOGREC entries from the time of the

error

Related referenceDSNJU003 (change log inventory) (Db2 Utilities)Related information00D10130 (Db2 Codes)

DSNR061I csect-name MEMBER ID member-idOF GROUP group-name ISINVALID. request-type REQUESTFAILED.

ExplanationA request to deactivate or destroy a member of a datasharing group specified an invalid member ID.


member-idThe member ID that was specified.

group-nameThe name of the data sharing group.

request-typeThe type of request: deactivate or destroy.

System actionThe request is ignored and is purged from the BSDS.Processing continues.

System programmer responseNo action is required.

DSNR062I csect-name MEMBER member-name ID member-id OF GROUPgroup-name CAN NOT BErequested-action BECAUSE IT ISNOT QUIESCED




ExplanationA request was made to deactivate or destroy a datasharing group member, but the member is notquiesced. Only a quiesced member can be deactivatedor destroyed.


member-name and member-idThe name and ID of the member that wasspecified.


requested-actionThe requested action, either DEACTIVATED (for adeactivation request) or DESTROYED (for adestruction request).

System actionThe request is ignored. Processing continues.


DSNR063I csect-name MEMBER member-name ID member-id OF GROUPgroup-name SUCCESSFULLYrequested-action

ExplanationThe request to deactivate or destroy a data sharinggroup member was successful.




requested-actionThe requested action, either DEACTIVATED (for adeactivation request) or DESTROYED (for adestruction request).



DSNR064I csect-name requested-action OFMEMBER member-name IDmember-id OF GROUP group-nameFAILED. REASON = reason-code

ExplanationA request was made to deactivate or destroy a datasharing group member, but the request was notsuccessful.


requested-actionThe requested action: DEACTIVATE or DESTROY.



reason-codeA hexadecimal code that indicates the reason forthe failure.

System actionThe request is ignored. Processing continues.

System programmer responseUse the information provided for the reason code toresolve the problem, then deactivate or destroy themember.

Problem determinationThe syslog and LOGREC from the time of the failuremight be necessary for diagnosis.


DSNR066I csect-name WARNING - EOMPROCESSING MIGHT BE STALLEDFOR JOBNAME = job-name, ASID =asid.

ExplanationEnd-of-memory (EOM) processing for an addressspace has been inactive for at least 4 minutes. TheEOM processing might be stalled, waiting for one ormore allied agents to complete abort processing.




job-nameThe name of the stalled job.

asidThe MVS address space identifier (ASID) of thestalled job.

Db2 cannot complete EOM processing for the addressspace until all allied agents in the address spaceterminate. However Db2 cannot terminate agentsundergoing abort processing until the abort actioncompletes. Db2 waits indefinitely for the abort tocomplete, to give long-running agents enough time tocomplete their processing with data integrity.

System actionWhile an address space is undergoing EOM processing,the recovery termination manager (RTM) checksperiodically to determine whether EOM processing forthe address space is inactive for more than 4 minutes.When that occurs, RTM abends the Db2 system agentwith ABEND30D. Db2 recovery logic retries the abendindefinitely for any must-complete allied agentswaiting for abort to complete. More than one addressspace might be in this condition. Db2 issues messageDSNR066I to the console for only one of the addressspaces it detects in this state.

The console might show other messages, such asDSNR048I, identifying the Units of Recovery (URs) for

this address space which are taking a long time tocomplete their processing. Other address spacespossibly encountering this condition might also beidentified from these messages. Db2 checks all theURs for the address space referenced in the message.It deletes the highlighted message for this addressspace when it detects that there are no more URs in apending abort condition for this agent.

System programmer responseDetermine whether EOM processing for the addressspace has been stalled too long, according to yourspecific system or application criteria. If it has, youmight need to terminate Db2. Terminating Db2 cancelsthe abort processing for the long running agents sothat EOM processing for the address space cancontinue.

When it restarts, Db2 must repeat the canceled abortprocessing to resolve the long running URs. However,you can postpone the back-out of the long runningURs, so that Db2 restart can complete first. For moreinformation, see Deferring restart processing (Db2Administration Guide).


Related tasksResolving postponed units of recovery (Db2Administration Guide)







Chapter 14. DSNS messagesMessage identifiers that begin with DSNS communicate information about the storage manager andindicate the progress of Db2 when storage parameters are being specified.

DSNS001I csect_name SUBSYSTEM HASEXCEEDED THE USER SPECIFIEDREAL STORAGE USAGETHRESHOLD

ExplanationYou have requested to perform real storage monitoringby specifying a non-zero value for subsystemparameter SPRMRSMX. Db2 has determined that theamount of real storage used has reached or exceededthe amount of combined real and auxiliary storageallowed.

System actionThe Db2 subsystem requests to record a Db2SYS1.LOGREC entry, and an RC00E20033 abend dumpis requested before Db2 subsystem termination isinitiated. The system terminates with:

*DSNV086E = DB2 ABNORMAL TERMINATION REASON=00E20033

System programmer responseDetermine whether the value specified for subsystemparameter, SPRMRSMX is realistic. If you decide tocontact IBM support, provide the Db2 SYS1.LOGRECentry and the RC00E20033 dump. Also, you will mostlikely be asked to provide IFCID225 records, whichshow historical storage usage, in order to determinewhat area is responsible for the real frame build up.

DSNS002I csect-name THE VALUE SPECIFIEDFOR SUBSYSTEM PARAMETERREALSTORAGE_MAX IS EQUAL ORGREATER THAN AVAILABLE REALSTORAGE

ExplanationThe value of the REALSTORAGE_MAX subsystemparameter is equal to or greater than the amount ofreal storage that is available to the address space.


System actionDb2 continues with normal startup.

System programmer responseIncrease the specified value if appropriate. Thespecified value might be normal if you expect thatmuch of the real storage usage for the installation is tobe paged out to auxiliary storage devices.

DSNS003I csect-nameSUBSYSTEM WARNINGTHRESHOLD FOR REAL STORAGEHAS BEEN DETECTED

ExplanationThe system has consumed a critical amount of the realand auxiliary storage that is allotted to this Db2subsystem by the REALSTORAGE_MAX subsystemparameter.


System actionProcessing continues but Db2 enters contraction modeif it is not already enabled. If real storage growthcontinues and reaches the limit defined by the value ofthe REALSTORAGE_MAX subsystem parameter, Db2terminates.


Operator responseIf appropriate, increase the value of theREALSTORAGE_MAX subsystem parameter, anddetermine why the real storage usage is approachingthe maximum allowed. If possible, reduce theworkload that is entering this Db2 member until thecondition is relieved.

Related referenceSubsystem parameters that are not oninstallation panels (Db2 Installation andMigration)Related informationDSNV516I


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_zparmnotonpanels.html



csect-name - BEGINNING STORAGECONTRACTION MODE

DSNS004I csect-name SUBSYSTEMTHRESHOLD FOR REAL STORAGERELIEVED

ExplanationThe real storage usage has dropped below the warningthreshold.



Operator responseDetermine why the shortage occurred and try toprevent that from happening again. Use IFCID 0225 toanalyze prior trends. The following trace fields arerelevant for this investigation:

• QW0225AX• QW0225ComStg_Aux• QW0225ComStg_Real• QW0225HVAuxSlots• QW0225HVPagesInReal• QW0225PriStg_Real• QW0225PriStg_Aux• QW0225RL• QW0225ShrStg_Real• QW0225ShrStg_Aux

Related referenceSubsystem parameters that are not oninstallation panels (Db2 Installation andMigration)Related informationDSNS003Icsect-nameSUBSYSTEM WARNING THRESHOLDFOR REAL STORAGE HAS BEEN DETECTED





Chapter 15. DSNT messagesMessage numbers that begin with DSNT communicate information about the service controller.

Messages issued by DSNTINST, DSNTINS1, and DSNTINS2 installation CLISTs use the following internalseverity levels:

0Successful execution: CLIST progress and tracing messages (processing continues)

4Warning: some adjustments might be made by the installation CLISTs (processing and JCL editingcontinues)

8Error: unable to continue (no JCL is edited)

DSNT000I program-name STARTED FORsubsystem-id SUBSYSTEM,VERSION db2-version (system-mode)

ExplanationThis informational message is returned at the start ofthe indicated program and reports information aboutthe Db2 version and the processing mode of the Db2subsystem that the program has connected to.


subsystem-idThe Db2 subsystem identifier.

db2-versionThe Db2 version.

system-modeThe current Db2 mode. Possible values are:CMn

Conversion mode, where n represents theversion of Db2 that is being migrated from.

NFMNew-function mode



DSNT001I program-name INTERNAL ERRORAT LOCATION location-nameBECAUSE OF UNEXPECTEDOBJECT OF TYPE object-type WITHNAME object-name

ExplanationThe program was terminated because an object wasnot expected.


location-nameDiagnostic information that identifies the functionthat was involved in the error.


object-nameThe name of the object, as either a specific nameor a qualified name:object-name is a specific name

SPECIFIC NAME name

object-name is a qualified namequalifier.name


User responseVerify that the latest maintenance has been applied,and apply maintenance if necessary. If the problempersists, contact IBM Support


DSNT002I program-name RECEIVED ANUNEXPECTED SQLCODE OF sql-code FROM THE sql-requestREQUEST


ExplanationDuring processing of an SQL request, the programreceived an unexpected SQL code. Further processinghas been halted.


sql-codeA numeric value that indicates why the SQLstatement execution was unsuccessful.

sql-requestAll or part of the SQL statement that was issued.For a long statement, only a portion of thestatement is provided.

System actionThe program rolls back all SQL changes andterminates.

User responseExamine the standard SQLCA diagnostic messages andoutput in the SYSPRINT output log at the point offailure to determine the cause of the error. Correct theerror and rerun the program.

Problem determinationThis message is followed by one or more of thestandard SQLCA diagnostic messages: DSNT404I,DSNT408I, DSNT411I, DSNT415I, DSNT416I,DSNT417I, and DSNT418I.


Related informationDSNT404ISQLCODE = sql-code, explanationDSNT408ISQLCODE = -sql-code, explanationDSNT411ISQLCAID = xxxx, SQLCA IDENTIFIERDSNT415ISQLERRP = xxxx, SQL PROCEDURE DETECTINGERRORDSNT416ISQLERRD = field-1, field-2, field-3, field-4,field-5, field-6 SQL DIAGNOSTIC INFORMATIONDSNT417ISQLWARNn-n SQL WARNINGSDSNT418ISQLSTATE = sqlstate, SQLSTATE RETURN CODE

DSNT003I DSNT003I DSNTRIN HASENCOUNTERED AN ERROR IN THECONTROL STATEMENT, DD = dd-name, ERROR = error-text, LINE =line-number, STATEMENT = error-statement

ExplanationDSNTRIN, the configuration tool for routines suppliedby Db2, encountered an error during configurationcontrol statement processing.

error-textAdditional information about the error. Expectedvalues include:

• CONTROL STATEMENT HAS AN INVALIDFORMAT

• ROUTINE NAME HAS AN INVALID FORMAT• CONTROL STATEMENT EXCEEDS 720 BYTES• NO VALUE FOUND FOR THE FIRST|SECOND|THIRD PARAMETER OR ONE OR MORECONTROL STATEMENTS WAS NOT SEPARATEDBY A BLANK LINE

• ONLY ONE PARAMETER FOUND• ACTUAL PARAMETERS: x, EXPECTEDPARAMETERS: y

• UNEXPECTED PARAMETER parameter-nameFOUND

• CONTROL STATEMENT FOR routine-nameNOT SUPPORTED

• CONTROL STATEMENT FOR routine-nameALREADY PROCESSED

• CONTROL STATEMENT FOR routine-nameNOT FOUND

line-numberThe location of the error.

dd-nameThe name of the data definition statement.

error-statementThe control statement in error.


User responseLocate the control statement in error at the indicatedline in the input allocated by the data definitionindicated by dd-name. Analyze the statement for theindicated error. Correct the problem, and resubmit jobDSNTIJRT to continue DSNTRIN processing.



Related conceptsJob DSNTIJRT (Db2 Installation and Migration)

DSNT004I DSNTRIN HAS SUCCESSFULLYCREATED object-type object-name

ExplanationDSNTRIN has successfully created the SQL object.



SPECIFIC NAME name




DSNT005I DSNTRIN HAS SKIPPEDprocessing-type PROCESSING OFobject-type object-name, REASON:reason-text

ExplanationDSNTRIN could not complete SQL processing for theindicated object.

processing-typeThe type of SQL processing that was attempted.



SPECIFIC NAME name


reason-textOne of the following reasons that the message wasissued:

The specified Db2 function level is required.REQUIRES NEW FUNCTION MODE

Db2 must be in new-function mode.RUN OPTIONS MAX LENGTH EXCEEDED

DSNTRIN cannot alter the RUN OPTIONS forthe SYSTOOLS.JSON_LEN function withXPLINK(ON) because the existing options plus',XPLINK(ON)' exceed the 254-charactermaximum length.


User responseIf reason-code is 10, run the job again after Db2 entersnew-function mode. Otherwise, no action is required.


DSNT006I DSNTRIN HAS GRANTED access-type ACCESS ON object-type object-name TO AUTHORIZATION IDSauthorization-ids

ExplanationDSNTRIN has granted access on one or more objectsto one or more authorization IDs as indicated in themessage.

access-typeThe access that was granted.



authorization-idsThe authorization IDs to which access wasgranted.


User responseReview the access given to ensure that it isappropriate for each authorization ID that it wasgranted. If the access is not appropriate, modify theGRANTTO parameter of the configuration controlstatement for each stored procedure or user-definedfunction that requires a different access list, andresubmit job DSNTIJRT.

Chapter 15. DSNT messages 459

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_jobdsntijrt.html



DSNT007I DSNTRIN HAS DROPPEDEXISTING object-type, object-name

ExplanationThe indicated object has been dropped. DSNTRINdrops existing objects only in REINSTALL mode orREINITIALIZE mode.



SPECIFIC NAME name




DSNT008I DSNTRIN HAS SET THE WLMENVIRONMENT FOR routine-typeschema.routine-name TOenvironment-name

ExplanationThe Db2-supplied stored procedure or user-definedfunction indicated by schema.routine-name has beenaltered to use the indicated WLM environment.

routine-typeThe type of routine: user-defined function orstored procedure.


SPECIFIC NAME name


environment-nameThe name of the WLM environment.


User responseReview the WLM environment setting for the routine toensure that it is appropriate. If the environment is notappropriate for the routine, modify the WLMENVparameter of the configuration control statement foreach stored procedure or user-defined function thatrequires to be run in a different WLM environment, andresubmit job DSNTIJRT.


DSNT009I DSNTRIN BIND PACKAGEREQUEST SUCCEEDED WITHRETURN CODE return-code FORCOLLECTION ID collection-id.package-id

ExplanationA bind request for the indicated package wascompleted.

return-codeThe return code issued by the command.

collection-id.package-idThe package that was bound.

Other messages related to the bind request mightprecede this message.

Multiple forms: This message has two forms. Theshort form is shown above. The long form is:

DSNTRIN BIND PACKAGE REQUEST SUCCEEDEDWITH RETURN CODE return-code FORCOLLECTION ID collection-id.package-idWITH OWNER owner-id

The long form of this message is issued if the OWNERoption was specified for the bind request.

owner-idThe package owner.








DSNT010I program-name request-typeREQUEST FOR collection-id.package-id FAILED WITHRETURN CODE return-code

ExplanationThe operation requested for the indicated packagewas rejected by Db2. Diagnostic messages from Db2precede this message.


request-typeThe type of request: BIND PACKAGE, BIND PLAN,FREE PACKAGE, or FREE PLAN.

collection-id.package-idThe package that could not be bound or freed.

return-codeA numeric value that indicates the reason for thefailure.

System actionThe request fails and processing terminates.

User responseReview the diagnostic messages from Db2, correct theproblem, and rerun the specified program.


Related informationAbout Db2 and related commands (Db2Commands)

DSNT011I program-name INPUTPARAMETERS ARE INVALID,REASON CODE = reason-code,TEXT = reason-text

ExplanationThe program encountered an error when it attemptedto process the input parameters that were passed to itin the PARM parameter or the SYSIN DD.


reason-code and reason-textThe reason code (reason-code) describes thecause of the error, and the reason text (reason-text) provides additional information that is specificto the reason code.

reason-code = 1The number of parameters specified isincorrect. The reason-text provides thefollowing additional information: number-passed PARAMETERS WERE PASSED BUTnumber-expected PARAMETERS AREEXPECTED, where:number-passed

The number of parameters that werepassed to the program.

number-expectedThe number of parameters that wereexpected by the program.

reason-code = 2A required parameter was not passed. Thereason-text provides the following additionalinformation: REQUIRED PARAMETERparameter-name WAS NOT PASSED, where:parameter-name

The name of the parameter that wasexpected, but that was not provided.

reason-code = 3An unrecognized parameter was passed. Thereason-text provides the following additionalinformation: UNRECOGNIZED PARAMETERparameter-name WAS PASSED, where:parameter-name

The name of the parameter that wasprovided where it was not expected.

reason-code = 4The value of one of the parameters is not valid.The reason-text provides the followingadditional information: THE VALUE FORPARAMETER parameter-name IS NOTVALID, where:parameter-name

The name of the parameter that is invalidwhere it was provided.

reason-code = 5The routine specified in DD:SYSIN is not a validDb2-supplied routine. The reason-text providesthe following additional information:schema.routine-name IS NOT A VALIDDB2-SUPPLIED ROUTINE, where:schema.routine-name

The name of the routine, qualified by thename of the schema in which the routinewas created.

6A parameter was specified two or more times.The reason-text provides the followingadditional information: PARAMETER




parameter-name WAS PASSED MORE THANONCE.

7The statement exceeded the maximum bytesallowed. The reason-text provides thefollowing additional information: STATEMENTEXCEEDS number-of-bytes BYTES


User responseCorrect the problem and run the program again.


DSNT012I program-name rrsaf-functionREQUEST FAILED. DSNRLIRETURN CODE = dsnrli-return,RRSAF RETURN CODE = rrsaf-return, RRSAF REASON CODE =rrsaf-reason

ExplanationThe program encountered an error when it attemptedto establish a connection to the Db2 subsystem.


rrsaf-functionThe Db2 Recoverable Resource ServicesAttachment Facility (RRSAF) function that wascalled.

dsnrli-returnA numeric value that indicates the reason for thefailure.

rrsaf-returnThe return code issued by Db2 Resource RecoveryServices attachment facility (RRSAF).

rrsaf-reasonThe reason code issued by the Db2 ResourceRecovery Services attachment facility (RRSAF). Formore information, see RRSAF return codes andreason codes (Db2 Application programming andSQL)

System actionThe program terminates.

User responseUse the return codes provided for DSNRLI and RRSAFto determine the problem, and proceed as instructed.


Related conceptsRRSAF return codes and reason codes (Db2Application programming and SQL)Db2 reason codes (Db2 Codes)

DSNT013I DSNTRIN FOR DB2 VERSIONprogram-version CANNOT BE RUNON DB2 VERSION db2-version

ExplanationThe code level of program DSNTRIN does not matchthe Db2 code level. For example, during migration to anew version of Db2, the program was executed on adownlevel member in data sharing coexistence mode.

program-versionThe version of the program.

db2-versionThe Db2 version.


User responseIn Db2 data sharing coexistence mode, run theprogram on a member that has been migrated to thenew version. Otherwise, verify that the load libraryspecified in the JOBLIB or STEPLIB for executing theprogram has the same code level as Db2.


DSNT014I program-name file-operation FILEERROR FOR DD:dd-name.DIAGNOSTIC TEXT diagnostic-text

ExplanationThe program encountered an error for the data setallocated to the data definition statement.









file-operationThe file operation during which the error occurred:OPEN, READ, WRITE, or CLOSE.


diagnostic-textAdditional diagnostic information for the error.

System actionThe file operation fails and the program terminates.

User responseCorrect the error indicated by the diagnostics, whichare provided by the IBM Language Environment.


Related referenceLanguage Environment Run-Time Messages(z/OS Language Environment Run-TimeMessages)

DSNT015I DSNTRIN PREVIEW OPTION WASSPECIFIED, THE install-typeACTION WAS NOT PERFORMED,INSTALL JCL WAS GENERATEDAND STORED IN stored-location

ExplanationThe Db2-supplied routines and supporting objectswere not installed, configured, or bound on the systembecause the preview option was specified. If a DDstatement called JCLOUT was specified in the JCL,then a JCL containing the actual SQL and BINDstatements that will be used to install the Db2-supplied routines is generated. A detailed report isalso written to SYSPRINT to which objects wereincluded for processing.

Multiple forms: This message has multiple forms. Inaddition to the standard form shown above, you mightsee the following form if no JCL job was generated:

DSNTRIN PREVIEW OPTION WAS SPECIFIED, THE install-type ACTION WAS NOT PERFORMED

install-typeThe type of installation performed.

stored-locationThe name of the data set and member where thegenerated installation job was stored.

System actionThe Db2-supplied routines and supporting objectswere not installed, configured, or bound. A reportdescribing impact to affected objects is written toSYSPRINT. Optionally, if the job included the JCLOUTDD statement, a JCL containing the actual SQL andBIND statements that can be used to install the Db2-supplied routines is generated.

User responseReview the report and verify which Db2-suppliedroutines and supporting objects are expected to becreated then resubmit the DSNTIJRT installation jobwithout the preview option or submit the generatedJCL if you are ready to install the Db2-suppliedroutines and supporting objects.

Related conceptsJob DSNTIJRT (Db2 Installation and Migration)Related tasksInstalling Db2-supplied routines duringinstallation (Db2 Installation and Migration)Installing Db2-supplied routines duringmigration (Db2 Installation and Migration)

DSNT016I DSNTXAZP THE CLIST INPUTMEMBER ds-name(member) WASSUCCESSFULLY CREATED

ExplanationDSNTXAZP has successfully created and stored theCLIST defaults input member.

ds-name(member)The name of the data set and member.

System actionThe CLIST defaults input member is generated and areport is written to SYSPRINT.

Processing continues.


DSNT017I DSNTXAZP AN ERROR WASENCOUNTERED DURINGPROCESSING, ERROR = error-text

ExplanationThe program encountered an error during processing.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ceea900/toc.htm




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_installdb2routinesinst.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_installdb2routinesinst.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_installdb2routinesmigr.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_installdb2routinesmigr.html

error-textAdditional information about the error. Expectedvalues include:

• THE DB2 VERSION AND THE VERSION OF THECLIST INPUT MEMBER ARE NOT THE SAME

• THE DB2 VERSION AND THE VERSION OFDSNTXAZP ARE NOT THE SAME

• FAILED TO CONNECT TO DB2• DSNWLI CALL FAILED, IFCARC1=ifcarc1,

IFCARC2=ifcarc2, IFCABNM=ifcabnm,IFCAGRSN=ifcagrsn, IFCAGBNM=ifcagbnm

• RETRIEVE FILE INFO FAILED (diagnostic-text)• INVALID ACTION 'action' WAS SPECIFIED• UNEXPECTED NUMBER OF PARAMETERS

FOUND (ACTUAL=number-found,EXPECTED=number-expected)

• MAXIMUM LENGTH FOR ACTION IS max-length• MAXIMUM LENGTH FOR SSID IS max-length• INSUFFICIENT MEMORY AVAILABLE• THE INPUT AND OUTPUT DATA SET MEMBER

ARE THE SAME• VERSION version IS NOT SUPPORTED

Tokens used within the error-text value include:

actionThe action that was specified.

diagnostic-textDiagnostic information for the failure.

number-foundThe number of parameters provided.

number-expectedThe number of parameters expected.

max-lengthThe maximum length permitted for theindicated object.

ifcagbnmA numeric value that indicates the number ofbytes that could not fit in the return area.

ifcabnmA numeric value that indicates the number ofbytes that could not fit in the return area.

ifcagrsnA numeric value that indicates the reason forthe failure.

ifcarc1 and ifcarc2Numeric values that indicate the reason for thefailure.

versionThe version that was specified.

System actionThe program terminates and the CLIST input memberis not created.

User responseUse the information provided in the message toidentify and resolve the problem.


DSNT018I DSNTRVFY - A WARNING WASENCOUNTERED DURING CALL TOROUTINE, WARNING = warning-text

ExplanationThe call to routine encountered a warning duringprocessing.

Multiple forms: This message has multiple forms. Inaddition to the standard form shown above, you mightsee the following form if no warning message isavailable:A WARNING WAS ENCOUNTERED DURING CALL TO ROUTINE

warning-textInformation about the warning.

System actionThe routine is validated.

User responseook for additional messages that might explain thecause of the warning or check the manuals foradditional information on the routine and proceed asinstructed by the message or documentation.

Severity4 (warning)

Related conceptsRoutines (Introduction to Db2 for z/OS)

DSNT019I DSNTRVFY - THE item FOUND IS'value-1', EXPECTED IS 'value-2'

ExplanationThe current value for an item does not match theexpected value.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_routinesintro.html

itemThe item where the discrepancy exists.

'value-1'The value that was found.

'value-2'The value that was expected


User responseDetermine what the expected value of the item is.

Verify that the installation job DSNTIJRT ran with thecorrect mode of installation.

Severity8 (error)

DSNT020I program-name THE CURRENTLYINSTALLED SERVICE DEFINITIONDOES NOT MATCH THE BASEID OFTHE EXTRACTED WLM SERVICEDEFINITION

ExplanationThe installed WLM service definition does not matchthe last extracted WLM service definition. Thiscondition happens if the WLM service definition wasupdated after the WLM service definition wasextracted.


System actionThe WLM service definition is not installed.

User responseResubmit the request.

Severity8 (error)

DSNT021I program-name WLM SERVICEPOLICY policy-name NOT FOUND

ExplanationThe WLM service policy that was supposed to beactivated was not found.


policy-nameThe name of the service policy.

System actionThe WLM service policy is not activated.

User responseIf you want to activate a WLM service policy, specify aname that is already defined to WLM.

Severity8 (error)

DSNT022I program-name WLM APPLICATIONENVIRONMENT wlm-environmentIS ALREADY DEFINED

ExplanationThe WLM application environment that was supposedto be added is defined to WLM.


wlm-environmentThe name of the existing WLM environment.

System actionThe WLM application environment is not added.

User responseIf you want to add a new WLM applicationenvironment, use a name that is not yet defined toWLM.

Severity4 (warning)

DSNT023I program-name requested-actionSUCCESSFUL

ExplanationThe action performed by the program was successful.


requested-actionThe action that was successful:


• ACTIVATE WLM POLICY policy-name, wherepolicy-name is the WLM policy.

• ADD WLM APPLICATION ENVIRONMENTenvironment-name, where environment-name isthe WLM environment name.

• REMOVE WLM APPLICATION ENVIRONMENTenvironment-name, where environment-name isthe WLM environment name.

• DISPLAY WLM INFORMATION• QUERY SERVICE POLICY

System actionThe action is processed.


DSNT024I program-name requested-actionFAILED

ExplanationThe action performed by the program failed.


requested-actionThe action that failed:

• ACTIVATE WLM POLICY policy-name, wherepolicy-name is the WLM policy.

• ADD WLM APPLICATION ENVIRONMENTenvironment-name, where environment-name isthe WLM environment name.

• REMOVE WLM APPLICATION ENVIRONMENTenvironment-name, where environment-name isthe WLM environment name.

• DISPLAY WLM INFORMATION• QUERY SERVICE POLICY


program-name requested-action FAILED -PROGRAM IS NOT APF-AUTHORIZED

The long form is used when the reason for the failure isAPF authorization.

System actionThe action is not processed.

User responseLook for additional messages that might explain thecause of the failure and proceed as instructed by themessages.

If the message includes the text PROGRAM IS NOTAPF-AUTHORIZED, make sure that the programresides in an APF-authorized library and that alllibraries in the STEPLIB or JOBLIB concatenation forthe job that invokes the program are APF-authorized.

Severity8 (error)

DSNT025I program-name WAS UNABLE TOPROCESS THE BIND OR FREEREQUEST, REASON CODE =reason-code

ExplanationThe program was not able to bind or free the packageor plan.



The data definition statement was missing.2

The OPEN request failed.3

The READ request failed.4

The request to retrieve file information failed.5

The call to the bind interface failed.771

A GETMAIN request was not successful.772

Unable to set up the bind interface.773

Unable to remove the bind interface.


program-name WAS UNABLE TO PROCESS THEBIND OR FREE REQUEST, REASON CODE =reason-code,DDNAME = dd-name,ERROR =error text

The long form is used during I/O operations (fileopening or closing).



error textDescription of error, generated during I/Ooperation. This text is sometimes a LanguageEnvironment error message.

System actionThe request fails and the program terminates.

User responseCorrect the error based on the information provided forthe reason-code value:

1Verify that the job used to execute the program hasallocated the SYSTSPRT data definition asSYSOUT=* and the SYSUT1 as a workfile withthese attributes:

//SYSUT1 DD UNIT=SYSDA,// SPACE=(32000,(30,30)),// DCB=(RECFM=VB,LRECL=133)

771Increase region, and resubmit the job.

All other valuesRespond according to the information received inerror text. The source of the information is:2, 3, or 4

IBM Language Environment5, 772, or 773

BIND interface


DSNT026I DSNTRVFY VALIDATION FORschema.routine-name WAS NOTPERFORMED BECAUSE THEROUTINE IS NOT ENABLED ONTHIS DB2 SUBSYSTEM

ExplanationThe indicated routine is currently defined with theDb2-reserved WLM application environment name ofDSNWLM_NOT_ENABLED, which indicates that theroutine is not enabled to run on this subsystem.Because the routine is not enabled to run on thissubsystem, validation processing is skipped.

schema.routine-nameThe name of the routine, qualified by the name ofthe schema in which the routine was created.

System actionThe routine is not validated.

User responseVerify that routine is intended to be disabled on thisDb2 subsystem. If it is not, change the WLMapplication environment to a valid one.

Severity4 (warning)

DSNT027I DSNTRVFY VALIDATION FORschema.routine-nameSUCCESSFUL

ExplanationThe validation for the indicated routine was successful.All validation steps completed successfully.




DSNT028I DSNTRVFY - WLM ENVIRONMENTDETAILS NAME environment-namePROC procedure-name STATE wlm-state NUMTCB wlm-numtcb

ExplanationThis message provides additional WLM informationabout the validated routine, and normally followsmessage DSNT027I, DSNT029I, or DSNT031I.


procedure-nameThe name of the WLM catalog procedure.

wlm-stateThe state of the WLM environment, such asACTIVE.

wlm-numtcbThe number of task control blocks, whichrepresents the number of tasks that can runsimultaneously in a single WLM address space.


System actionAdditional WLM information is displayed.


Related informationDSNT027IDSNTRVFY VALIDATION FOR schema.routine-name SUCCESSFULDSNT029IDSNTRVFY VALIDATION FOR schema.routine-name COMPLETED WITH WARNINGSDSNT031IDSNTRVFY VALIDATION FOR schema.routine-name FAILED

DSNT029I DSNTRVFY VALIDATION FORschema.routine-name COMPLETEDWITH WARNINGS

ExplanationThe validation for the indicated routine completed withone or more warnings. Some validation stepscompleted successfully, but others did not.



User responseLook for additional messages that might explain thecause of the warnings and proceed as instructed bythe messages.

Severity4 (warning)

DSNT030I DSNTRVFY - THE ROUTINE IS NOTDEFINED TOSYSIBM.SYSROUTINES

ExplanationThe routine that is identified by schema.routine-namein message DSNT031I was not defined to theSYSIBM.SYSROUTINES catalog table. This messagenormally follows message DSNT031I.

System actionProcessing continues with the next routine.

User responseDetermine if the routine identified in messageDSNT031I is the intended one. If it is not, correct theerror, and resubmit the DSNTIJRT installation job.

Severity8 (error)

Related informationDSNT031IDSNTRVFY VALIDATION FOR schema.routine-name FAILED

DSNT031I DSNTRVFY VALIDATION FORschema.routine-name FAILED

ExplanationThe validation of the routine was not successful.


System actionThe routine is not validated. Processing continues.

User responseLook for additional messages that might explain thecause of the failure and proceed as instructed by themessages.

Severity8 (error)

DSNT032I DSNTRVFY - THE CALL TOROUTINE WAS SUCCESSFUL

ExplanationThe routine was successfully called.




DSNT033I program-name program-typeENDED, RETURN CODE = return-code

ExplanationThe specified batch program has completed.

program-nameThe type of program executed.

program-typeThe type of program.

return-codeThe most severe return code encountered at anytime during processing.

System actionThe n program terminates.

User responseIf the return code is 4 or higher, look for othermessages that might explain the cause of the warningor failure, and proceed as instructed by the message.

DSNT034I DSNTRVFY - AN ERROR WASENCOUNTERED DURING CALL TOROUTINE, SQLCODE = sql-code

ExplanationThe call to routine encountered an SQL error duringprocessing.

sql-codeA numeric value that indicates why the SQLstatement execution was unsuccessful.

Multiple forms: This message has multiple forms. Inaddition to the standard form shown above, you mightsee one of the following forms if no SQL return code isavailable:AN ERROR WAS ENCOUNTERED DURING CALL TO ROUTINEAN ERROR WAS ENCOUNTERED DURING CALL TO ROUTINE,ERROR = error-text

error-textInformation about the error.


User responseUse the information provided for the SQL error code toresolve the problem.

Severity8 (error)

Related conceptsSQL error codes (Db2 Codes)

DSNT035I DSNTRVFY VALIDATIONPROGRAM FAILED TO INITIALIZE,REASON CODE = reason-code

ExplanationThe validation program failed to complete initializationbecause of errors.

reason-codeA numeric value that indicates the reason for thefailure.1

There is insufficient memory to run theprogram.

2This version of Db2 is not supported by theprogram.

3The program was unable to process the SYSINDD input.

4An error was encountered during extendedconsole processing.

5The bind request for DSNTRVFY failed.

6The program is not APF-authorized.

System actionThe routine validation program terminates.

User responseUse the reason code to determine the cause of theerror. Look for additional messages in the job output,on the system console, or on the operator console.Correct the problem, and run the program again.


DSNT036I DSNTRVFY IGNORED ROUTINEschema.routine-name IN LINE line-number BECAUSE THE ROUTINEALREADY EXISTS


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_n.html

ExplanationThe routine was already included for validation. Theduplicate routine will be ignored.


line-numberThe line where the second instance ofschema.routine-name was found.

System actionThe duplicate routine is not selected and processingcontinues.

User responseRemove the duplicate name from the SYSIN DD. If youplan to reuse the job, remove the duplicate name fromthe SYSIN DD before you rerun the job.

Severity4 (warning)

DSNT037I program-name action WLMSERVICE DEFINITION REQUESTFAILED, MACRO = macro-name,RETURN CODE = return-code,REASON CODE = reason-code

ExplanationAn error was encountered during execution of a WLMmacro.


action and macro-nameThe action that was attempted and the WLM macrothat was used:

action macro-name

ACTIVATE IWMPACT

EXTRACT IWMDEXTR

INSTALL IWMDINST

QUERY IWMPQRY

return-codeThe severity or type of failure.



program-name action WLM SERVICEDEFINITION REQUEST FAILED, MACRO = macro-name, RETURN CODE = return-code, REASONCODE = reason-code, VALIDATE RSN =validate-reason, VALIDATE OFFSET =validate-offset

The long form of the message is issued when action isINSTALL.

validate-reasonA hexadecimal reason code that identifies thespecific error in the input service definition foundduring validity checking.

validate-offsetLocation in the service definition file where thevalidation error occurred. This value is the offsetfrom the beginning of the service definition(IWMSERVD) to the section of the input servicedefinition where validity check processing found anerror described by the reason code returned invalidate-reason.


User responseUse the information provided for the macro identifiedby macro-name to resolve the problem.


Related referenceIWMDEXTR Return and Reason Codes (MVSProgramming: Workload Management Services)IWMDINST Return and Reason Codes (MVSProgramming: Workload Management Services)IWMPACT Return and Reason Codes (MVSProgramming: Workload Management Services)IWMPQRY Return and Reason Codes (MVSProgramming: Workload Management Services)

DSNT038I DSNTRVFY - THE WLMENVIRONMENT environment-nameIS NOT AVAILABLE

ExplanationThe WLM application environment is either not definedor is not available.












System actionThe routine is not validated. Processing continues withthe next routine.

User responseIssue the following MVS system command todetermine if the WLM application environment isdefined:

D WLM,APPLENV=environment-name

If the environment is not defined, use one of thefollowing methods to define it:

• Use the WLM administrative application, IWMARIN0.• Modify and submit the sample JCL DSNTIJRW.

If the environment is defined but the status is reportedas not available, determine what caused the WLMapplication environment to become unavailable,correct the problem, and issue the VARY WLM MVSsystem command to reset the status.

Severity8 (error)

DSNT039I THE CALL TO THE ROUTINE WASNOT PERFORMED

ExplanationThe routine will not be called as part of validation forone or more of the following reasons:

• Optional system support, such as CICS, IMS, or IBMMQ, is required.

• External setup on a remote server or workstation isrequired.

• A call could introduce or modify data unexpectedlyin a production environment.

The message that precedes this one identifies theroutine that was skipped.

System actionThe routine is not called. Processing continues.


Related informationDSNT027I

DSNTRVFY VALIDATION FOR schema.routine-name SUCCESSFULDSNT029IDSNTRVFY VALIDATION FOR schema.routine-name COMPLETED WITH WARNINGS

DSNT040I time DSNTRVFY ROUTINEVALIDATION SUMMARY STATUSSCHEMA SPECIFIC NAME

ExplanationThis message displays a summary of which Db2routines completed successfully, which onescompleted with warnings, and which ones failed.

timeThe time at which the message was issued, in theformat hh.mm.ss.

The message is formatted with column headings anddividing lines:

STATUS SCHEMA SPECIFIC NAME-- -------- -------- ---------------

Each line begins with a character that identifies theresult:

/Success

XFailure

*Warning



DSNT041I DSNTRVFY VALIDATION FORschema.routine-name WAS NOTPERFORMED BECAUSE THECURRENT MODE IS NOTSUPPORTED

ExplanationThe validation for the routine was skipped because theDb2 level that is required by the routine does notmatch the current mode.



The required mode is dependent on the storedprocedure that is being validated.


User responseWait until new function is activated, then run theDSNTIJRV validation job again to validate the routine.

Wait until Db2 enters the required mode indicated inthe message, then run the DSNTIJRV validation jobagain to validate the routine.

Severity4 (warning)

DSNT042I DSNTRVFY - THE COLLECTION IDUSED TO BIND THE PACKAGEDOES NOT MATCH THECOLLECTION ID DEFINED INSYSIBM.SYSROUTINES

ExplanationThe collection ID that is defined in theSYSIBM.SYSROUTINES catalog table for the routinedoes not match the collection ID used to bind thepackage.


User responseDetermine if the collection ID that was used to bindthe package is appropriate, and correct it if it is not.

Severity4 (warning)

DSNT043I DSNTRVFY - THE WLMAPPLICATION ENVIRONMENT ISSHARED WITH ANOTHERROUTINE THAT HAS A DIFFERENTSECURITY REQUIREMENT

ExplanationThe following Db2-supplied routines requires RACFprogram control if the BPX.DAEMON facility class isactive. If the BPX.DAEMON is active and one of theprograms loaded into the WLM address space wherethese Db2-supplied routines are running is not defined

to program control then an error will be returned bythe routine indicating that the operation is notpermitted.

• SYSPROC.ADMIN_COMMAND_UNIX• SYSPROC.ADMIN_JOB_CANCEL• SYSPROC.ADMIN_JOB_FETCH• SYSPROC.ADMIN_JOB_QUERY• SYSPROC.ADMIN_JOB_SUBMIT• SYSPROC.ADMIN_UTL_MONITOR


User responseDetermine if the BPX.DAEMON is active. IfBPX.DAEMON is not active, no action is required.

If it is active, ensure that all programs that have beenloaded into the WLM address space where theseroutines are defined are controlled by RACF. Refer tothe DSNTIJRA job, which provides the commands fordefining programs to RACF program control.

Severity4 (warning)

DSNT044I DSNTRVFY - THIS ROUTINEREQUIRES A WLM ENVIRONMENTNUMTCB SETTING OF 1

ExplanationThe routine requires NUMTCB=1, but the routine wasrun on a WLM application environment were theNUMTCB is not set to 1.


User responseVerify that the NUMTCB setting of the WLM applicationenvironment assigned to the routine is 1. If theNUMTCB setting is not 1, either change the NUMTCBsetting to 1 or assign the routine to a WLM applicationenvironment where the NUMTCB setting is 1.

Severity8 (error)

DSNT045I DSNTRVFY - THE NUMTCBSETTING IS NOT WITHIN THE


RECOMMENDED RANGE OFrecommended-range

ExplanationThe routine was assigned to a WLM applicationenvironment where the NUMTCB setting is not withinthe recommended range.

recommended-rangeThe recommended range for NUMTCB. In themessage, this value is expressed in one of thefollowing forms:minimum TO maximum

The recommended range is indicated byspecific lower and upper values.

minimum OR MOREThe recommended range is the indicated valueor any greater value.


User responseVerify the NUMTCB setting of the WLM applicationenvironment assigned to the routine. If the NUMTCBsetting is not within the recommended range, eitherchange the NUMTCB setting to any value within therecommended range or assign the routine to a WLMapplication environment that has a NUMTCB settingthat is within the recommended range.

Severity4 (warning)

DSNT046I DSNTRVFY - THE WLMAPPLICATION ENVIRONMENT ISNOT APF-AUTHORIZED

ExplanationThe routine requires an APF-authorized environmentbut the assigned WLM application environment is notAPF-authorized.


User responseDetermine if the WLM application environmentassigned to the routine is APF-authorized. If it is notAPF-authorized, either modify the WLM procedure to

make it APF-authorized, or assign the routine to a WLMapplication environment that is APF-authorized.

Severity8 (error)

DSNT047I DSNTRVFY - THE WLMAPPLICATION ENVIRONMENT ISAPF-AUTHORIZED

ExplanationThe routine requires an environment that is not APF-authorized, but the assigned WLM applicationenvironment is APF-authorized.


User responseDetermine if the WLM application environmentassigned to the routine is APF-authorized. If it is APF-authorized, either modify the WLM procedure to makeit not APF-authorized, or assign the routine to a WLMapplication environment that is not APF-authorized.

Severity8 (error)

DSNT048I DSNTRVFY - THE DD STATEMENTdd-name WAS NOT FOUND

ExplanationThe routine requires that the indicated data definition(DD) statement is defined to the WLM storedprocedure address space, but the statement was notallocated.


If a diagnostic message from the IBM LanguageEnvironment service is available, that message followsDSNT048I. This additional message provides specificinformation about the failure that can be used to helpdiagnose the cause.


User responseDetermine whether the WLM application environmentthat is assigned to the routine contains the DD


statement indicated by dd-name. If it does not containthe required DD statement, either modify the WLMprocedure to include the DD statement or assign theroutine to a WLM application environment thatcontains the DD statement.

Otherwise, if an additional message from the IBMLanguage Environment service is provided, use thatmessage to diagnose and correct the problem.

Severity8 (error)

DSNT049I DSNTRVFY - JAVA VERSION (java-version)

ExplanationThe WLM application environment to which the Java™

routine is assigned is configured correctly for Java, andthe indicated version of Java was found.

java-versionThe version of Java that is available to the WLMenvironment.



DSNT050I DSNTRVFY - JAVA NOT ENABLEDON WLM ENVIRONMENTenvironment-name

ExplanationThe WLM application environment to which the Javaroutine is assigned is not configured correctly for Java.



User responseModify the WLM catalog procedure that starts the WLMstored procedure address space to include theJAVAENV data definition statement.

Severity8 (error)

Related tasksSetting up the environment for Java routines(Db2 Application Programming for Java)

DSNT051I program-name ACTIVE WLMSERVICE DEFINITION SERVICEDEFINITION NAME definition-name INSTALLED ON timestampINSTALLED BY user-id INSTALLEDFROM system-name NUMBER OFAPPLICATION ENVIRONMENTenvironment-count

ExplanationThis message is returned by the indicated program asa response to a request to display WLM information.


definition-nameThe name of the WLM service definition.

timestampThe date and time when the service definition wasinstalled, in the format yyyy-mm-dd-hh.mm.ss.nnnnnn.

user-idThe user ID of the service administrator whoinstalled the service definition.

system-nameThe name of the system on which the servicedefinition was installed.

environment-countThe number of application environments that aredefined.

This message is issued in response to either the batchprogram DSNTWLMB or the stored procedureDSNTWLMS (SYSPROC.DSN_WLM_APPLENV) whenWLMINFO is specified.



DSNT052I program-name THE AUTHIDSPECIFIED, authorization-id,DOES NOT HAVE INSTALLATIONSYSTEM ADMINISTRATORAUTHORITY


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/java/src/tpc/imjcc_javaroutineenvironment.html


ExplanationThe indicated authorization ID, which was specified inthe AUTHID parameter for the indicated program, isnot a Db2 installation system administrator ID. Inorder to be marked as system defined, storedprocedures and user-defined functions need to becreated or altered using Db2 installation systemadministrator authority.


authorization-idThe specified authorization ID.

System actionDb2-supplied stored procedures and user-definedfunctions that are created or altered by this routine arenot marked as system defined.

User responseIf Db2-supplied stored procedures and user-definedfunctions at your site need to be marked as systemdefined, change the AUTHID parameter to a Db2installation system administrator ID and run jobDSNTIJRT again.

Severity4 (warning)

Related conceptsJob DSNTIJRT (Db2 Installation and Migration)Job DSNTIJRV (Db2 Installation and Migration)Related referenceCommon Db2 administrative authorities(Managing Security)

DSNT053I DSNTRIN WAS UNABLE TOPROCESS THE IFI READSREQUEST FOR IFCID 106: RETURNCODE = return-code, REASONCODE = reason-code, BYTES NOTMOVED = bytes-remaining

ExplanationDSNTRIN attempted to perform a synchronous read ofIFCID trace record 106 but received an unexpectedreturn code from the Db2 Instrumentation FacilityInterface (IFI).return-code

The return code from IFI.reason-code

The reason code from IFI.

bytes-remainingThe number of bytes that did not fit in the returnarea and still remain in the buffer.

System actionDSNTRIN terminates.

User responseTo diagnose the error, refer to the return and reasoncodes for information about the IFCARC1 andIFCARC2 values in the instrumentation facilitycommunications area (IFCA). Rerun job DSNTIJRTwhen the cause has been corrected.

Severity8 (error)

Related conceptsX'E6......' codes (Db2 Codes)Job DSNTIJRT (Db2 Installation and Migration)Related referenceInstrumentation facility communications area(IFCA) (Db2 Performance)

DSNT054I program-name ONE OR MORESUPPORTING OBJECTS WEREIDENTIFIED FOR UPDATE, AREBIND MAY BE REQUIRED FORPACKAGES THAT REFERENCETHESE OBJECTS

ExplanationThe program identified one or more supporting objectsfor update while in preview mode and the program cannot determine whether packages will be invalidated asa result of the update.



User responseIf the ABIND subsystem parameter is set to NO andyou use the generated JCL to install or update theDb2-supplied routines, then you need to resubmit theDSNTIJRT installation job afterwards with theMODE(INSTALL-PREVIEW) option. That actionidentifies and generates BIND statements for anypackages that were invalidated. Finally, you mustprocess the generated BIND statements.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_jobdsntijrv.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_commondb2adminauthorities.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_commondb2adminauthorities.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_00e6.html




If the ABIND subsystem parameter is set to YES, or ifyou run the DSNTIJRT job without the PREVIEWoption, then no action is required because Db2 rebindsany invalidated package automatically.

Severity4 (warning)

Related conceptsJob DSNTIJRT (Db2 Installation and Migration)Changes that invalidate packages (Db2Application programming and SQL)Automatic rebinds (Db2 Applicationprogramming and SQL)Related referenceAUTO BIND field (ABIND subsystem parameter)(Db2 Installation and Migration)

DSNT055I DSNTRIN HAS BYPASSED THECONFIGURATION CONTROLSTATEMENT FOR OBSOLETEROUTINE schema-name.routine-name

ExplanationProgram DSNTRIN encountered a configuration controlstatement for an obsolete Db2-supplied storedprocedure or user-defined function.

schema-nameThe name of the table schema or creator.

routine-nameThe name of the user-defined function or storedprocedure.

System actionThe statement is ignored. Processing continues.

User responseRemove the configuration control statement for theobsolete routine.

Severity4 (warning)

DSNT056I program-name AN ALTERREQUEST HAS PLACED TABLESPACE database-name.tablespace-name IN ADVISORY REORGPENDING STATUS

ExplanationThe table indicated in a preceding message has beenchanged with an SQL alter statement by the programindicated by program-name. The containing tablespace, database-name.tablespace-name, is availablebut the definition changes have not yet been applied.



tablespace-nameThe name of the table space.

System actionThe table space is placed in pending definition status.Processing continues.

User responseRun the REORG TABLESPACE utility with SHRLEVELCHANGE or SHRLEVEL REFERENCE on the entire tablespace to materialize the pending definition changes.

DSNT057I DSNTMVSB PROGRAM ENDED,RETURN CODE = return-code,COMMAND COMPLETION CODE =command-completion-code.

ExplanationThe batch program DSNTMVSB has completed.return-code

The return code encountered during processing:return-code

0

The batch program did not encounter anyerrors during processing.

command-completion-code is set to 0 or 4.

4The batch program issued the commandbut was unable, within the prescribed waittime, to determine the command executionstatus based on the command messagesretrieved. All command messages and anyDb2 MSTR / IRLM job status messagesretrieved within the prescribed wait timeare written to DD:CMDOUT.

command-completion-code is set to 8 or16.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_changesinvalidateplanspkgs.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_automaticrebinding.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_abind.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_abind.html

8The batch program issued the commandbut was unable to determine the commandexecution status due to an internal error.All the command messages and any Db2MSTR / IRLM job status messages retrievedso far are written to DD:CMDOUT.

command-completion-code is set to 8 or16.

12The batch program encountered an errorduring processing. A message describingthe error is written to SYSPRINT.

16The batch program did not encounter anyerrors during processing. However, thecommand completed abnormally.

command-completion-code is set to 12.

command-completion-code0

The command completed successfully.

Table 2. Details for command-completion-code 0

Command command-completion-codemeaning

Messagereceived

START DB2 Successfulcompletion

DSN9022Icmd_prefix

STOP DB2 Successfulcompletion

DSN9022Icmd_prefix

If Db2 MSTRaddress spaceterminationmonitoring isrequested:message'ssnmMSTRNOTFOUND' wasfound in the 'D J,ssnmMSTR'commandoutput.

4

The command was not processed. Forexample, Db2 was already stopped whenSTOP DB2 was requested.



Messagereceived

START DB2 Db2 was alreadyactive when thecommand wasissued.

DSNY003Icmd_prefix


Table 3. Details for command-completion-code 4(continued)


Messagereceived

STOP DB2 When thecommand wasissued, Db2 wasalready stoppedor Db2 was inthe process ofstopping and itstoppedsuccessfully.

If Db2 MSTR orIRLM addressspaceterminationmonitoring is notrequested, anyof the followingmessages arereceived:

• DSN3106Icmd_prefix

• DSNY004Icmd_prefix andDSN9022Icmd_prefix

If Db2 MSTRaddress spaceterminationmonitoring isrequested, bothof the followingmessages werereceived:

• DSNY004Icmd_prefixandDSN9022Icmd_prefix

• 'ssnmMSTRNOT FOUND' in'D J,ssnmMSTR'commandoutput

If IRLM addressspaceterminationmonitoring isrequested, bothof the followingmessages werereceived:

• DSNY004Icmd_prefixandDSN9022Icmd_prefix



Messagereceived

• 'irlm_jobNOT FOUND'in 'D J,'irlm_job'commandoutput

8

The command started but the completionstatus is unknown.



Messagereceived

Expectedmessagenotreceived

START DB2 Db2 is inthe processof starting,but thecompletionstatus ofthe STARTDB2command isunknown.

DSNY024Icmd_prefix

Any of thefollowingmessages:


• DSNV086Ecmd_prefix







Messagereceived


STOP DB2 Db2 is inthe processof stopping,but thecompletionstatus ofthe STOPDB2command isunknown.

One of thefollowingmessageswasreceived:

• DSNY002Icmd_prefix

• DSNY004Icmd_prefix

One of thefollowingmessageswas notreceived:



OrDSN9022Icmd_prefixwasreceivedalong withone of thefollowingconditions:

• Db2 MSTRaddressspaceterminationmonitoring isrequested, and'ssnmMSTR NOTFOUND'was notfound in'D J,ssnmMSTR'commandoutput

• IRLMaddressspaceterminationmonitorin



Messagereceived


g isrequested, and'irlm_job NOTFOUND' isnot foundin 'D J,'irlm_job'commandoutput.

12

The command completed abnormally.



Messagereceived

START DB2 Abnormalcompletion.

One of thefollowingmessages wasreceived:


• DSNV086Ecmd_prefix





STOP DB2 Abnormalcompletion.

One of thefollowingmessages wasreceived:




16

The command output does not satisfy theconditions that are listed for command-completion-code 0, 4, 8, or 12.

command-completion-codeThe completion status of the command.


User responseUse the information provided for the return-code andcommand-completion-code to determine the status ofcommand execution.

Related referenceDSNTMVSB tool (Db2 Installation andMigration)-START DB2 (Db2) (Db2 Commands)-STOP DB2 (Db2) (Db2 Commands)

DSNT058I DSNTRIN PROCESSING CANNOTBE CONTINUED BECAUSE routine-type routine-name IS DEFINEDWITH AN UNEXPECTED VERSION,version-identifier. THE STATUS ISversion-status.

ExplanationDuring preliminary processing, DSNTRIN detected aDb2-supplied native SQL procedure or compiled SQLscalar function that has an unexpected version. Thissituation usually indicates that a local version of theroutine was created. However, Db2 supports onlyofficial versions of Db2-supplied routines soprocessing terminates.

routine-typeThe type of routine, SQL PROCEDURE or SQLFUNCTION

routine-nameThe schema and specific name of the routine

version-identifierThe version identifier of the unexpected version

version-statusThe status of the unexpected version, ACTIVE orINACTIVE

System actionProcessing is discontinued.

User responseDrop the indicated unexpected version of the routineand rerun DSNTRIN:

1. If the unexpected version is the active version, useone of the following statements to activate theofficial version, V1:

• If the routine type is SQL PROCEDURE:

ALTER PROCEDURE routine-name ACTIVATE VERSION V1

• If the routine type is SQL FUNCTION:

ALTER SPECIFIC FUNCTION routine-name ACTIVATE VERSION V1

2. Use one of the following statements to drop theunexpected version:

• If the routine type is SQL PROCEDURE:

ALTER PROCEDURE routine-name DROP VERSION version-identifier

• If the routine type is SQL FUNCTION:

ALTER SPECIFIC FUNCTION routine-name DROP VERSION version-identifier


Related conceptsJob DSNTIJRT (Db2 Installation and Migration)Related referenceReserved schema names (Db2 SQL)Procedures that are supplied with Db2 (Db2SQL)

DSNT059I program-name WLM APPLICATIONENVIRONMENT wlm-environmentIS NOT DEFINED

ExplanationThe WLM application environment that was specifiedto be deleted is not defined to WLM.


wlm-environmentThe name of the WLM application environment.

System actionNo WLM application environment is removed.

The return code for the program-name programdepends on the option that was specified:


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntmvsb.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntmvsb.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_startdb2.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_stopdb2.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_reservedschemanames.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_suppliedstoredprocedures.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_suppliedstoredprocedures.html

• 4 (warning) for REMOVE_IF_EXISTS orREMIFEXISTS_ACTIVATE

• 8 (error) for REMOVE or REMOVE_ACTIVATE

User responseIf you want to remove a WLM application environment,use a name that is defined to WLM.

Severity :4 (warning) or 8 (error)

Related referenceDSN_WLM_APPLENV stored procedure (Db2SQL)DSNTWLMB tool (Db2 Installation andMigration)

DSNT089I DSNTXTA HAS RECREATEDEXPLAIN TABLE INDEX schema-name.index-name ON schema-name.table-name (key-list)

ExplanationThe EXPLAIN table index has been dropped and re-created in order to imbed additional keys. Theseactions are performed only when ALTER INDEX cannotbe used to update the index.schema-name

The name of the table and index schema orcreator.

index-nameThe name of the index.


key-listThe names of the columns, in sequence, used torecreate the index.




Related tasksSetting up the environment for Java routines(Db2 Application Programming for Java)

DSNT090I DSNTXTA REQUEST CANCELLEDBECAUSE THERE ARE NO EXPLAINTABLES IN SCHEMA schema-name

ExplanationThe request was cancelled because there are noEXPLAIN tables in the specified schema.



User responseVerify that you have specified the correct value for theDSNTXTA schema name parameter. If it is correct,then no further action is required for that schema.

Severity4 (warning)

DSNT091I DSNTXTA HAS ALTERED EXPLAINTABLE schema-name.table-name.COLUMN column-name WASchange-description

ExplanationThe EXPLAIN table has been modified as indicated.



column-nameThe name of the column.

change-descriptionThe alteration that was made to the EXPLAINtable:RENAMED TO new-name

The column was renamed.new-name

The new name of the column.CHANGED FROM old-type TO new-type

The data type of the column was changed.old-type

The data type used for the column beforethe change.

new-typeThe data type used for the column after thechange.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_dsnwlmapplenv.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_sp_dsnwlmapplenv.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntwlmb.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntwlmb.html



ADDED AS data-typeThe column was added to the database.data-type

The data type used for the new column.




DSNT092I DSNTXTA DID NOT COMPLETEPROCESSING OF schema-name.table-name BECAUSEreason-text.

ExplanationThe EXPLAIN table could not be updated to therequired format for this version of Db2 for theindicated reason.



reason-textThe reason for that the table could not be updated:IT CANNOT BE ALTERED TO A 10-COLUMNTABLE

A 9-column DSN_QUERY_TABLE exists in theindicated schema. A 9-columnDSN_QUERY_TABLE cannot be altered to a 10-column DSN_QUERY_TABLE because the newcolumn, GROUP_MEMBER, must reside atposition 8.

OF AN UNEXPECTED NAME OR TYPE FORCOLUMN NUMBER column-number. EXPECTED:expected-format. FOUND: actual-format.

While analyzing a table, DSNTXTA encountereda column that has an unexpected name orattributecolumn-number

The location of the unexpected name orattribute.

expected-formatThe format that is required for the name orattribute.

actual-formatThe format that is used for the name orattribute.

COLUMN column-name CANNOT BE ADDEDPRIOR TO NEW-FUNCTION MODE

Db2 is in a mode prior to new-function-mode.The column cannot be added until Db2 entersnew-function-modecolumn-name

The name of the column.

System actionProcessing of the table that is identified by schema-name.table-name is discontinued. Processingcontinues with the next candidate table, if one exists.

User responseTake the action that is indicated for the reason-textvalue:

IT CANNOT BE ALTERED TO A 10-COLUMN TABLEUse REXX exec DSNTXTB to generate statementsfor migrating the 9-column DSN_QUERY_TABLE toa 10-column DSN_QUERY_TABLE. See jobDSNTIJXB for an example of how to executeDSNTXTB, and job DSNTIJXC for an example ofhow to process the generated statements after youhave reviewed them and made any requiredadjustments.

OF AN UNEXPECTED NAME OR TYPE FOR COLUMNNUMBER column-number. EXPECTED: expected-format. FOUND: actual-format.

Either the table is not an EXPLAIN table or it is notin the expected format.

1. Query SYSIBM.SYSCOLUMNS, and inspect thecolumn names and attributes of the table. Forexample, use the following query:

SELECT NAME, COLNO, CASE COLTYPE WHEN 'TIMESTMP' THEN 'TIMESTAMP' ELSE COLTYPE END, LENGTH ,LENGTH2 FROM SYSIBM.SYSCOLUMNS WHERE TBCREATOR = 'schema-name' AND TBNAME = 'table-name' ORDER BY COLNO;

Use the information aboutSYSIBM.SYSCOLUMNS to help you locate thestructural problem.

2. If you suspect that the table might not be anEXPLAIN table, review the list of EXPLAINtables. Compare your table to the expectedtable of the same name. If the table is not anEXPLAIN table, consider renaming it.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsyscolumnstable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/usrtab/src/tpc/db2z_explaintables.html


3. If the table is an EXPLAIN table, it is not in theexpected format and you must correct thediscrepancy. You can either:

• Alter the table to conform to the formatdescribed for the table.

• Rename the existing table, create areplacement table with the appropriate namein the expected format, and copy the datafrom the original table to the replacement.When you have confirmed the contents of thereplacement table, drop the original table.

COLUMN column-name CANNOT BE ADDED PRIORTO NEW-FUNCTION MODE

Rerun this job when Db2 enters new-functionmode.

Severity4 (warning)

DSNT093I DSNTXTA PROCESSINGCOMPLETE. SCHEMAS EXAMINED:total-schemas; TABLESEXAMINED: total-tables; TABLESALTERED: total-altered; INDEXESEXAMINED: total-indexes;INDEXES RECREATED: total-recreated; TOTAL WARNINGS:total-warnings; TOTAL ERRORS:total-errors

ExplanationAll EXPLAIN tables in the specified schema orschemas are now in the current format, except asnoted by previous warning messages. This messagereports summary statistics for the DSNTXTA job.

total-schemasThe total number of schemas that were processed.

total-tablesThe total number of tables that were processed.

total-alteredThe total number of tables that were altered.

total-indexesThe total number of indexes that were processed.

total-recreatedThe total number of indexes that were re-created.

total-warningsThe total number of warnings that were issued.

total-errorsThe total number of errors that were issued.


User responseReview the summary statistics and other DSNTmessages that were generated during processing.These messages identify tables that were not updated.


DSNT094I DSNTXTB REQUEST CANCELLEDBECAUSE THERE ARE NO EBCDICEXPLAIN TABLES IN SCHEMAschema-name

ExplanationThe request was cancelled because there are noEBCDIC EXPLAIN tables in the specified schema.



User responseVerify that you have specified the correct value for theDSNTXTB schema name parameter. If it is correct,then no further action is required for that schema.

Severity4 (warning)

DSNT095I DSNTXTB REQUEST CANCELLEDBECAUSE TABLE schema-name.table-name IS NOT IN THEREQUIRED FORMAT AT COLUMNNUMBER column-number.EXPECTED: expected-format.FOUND: actual-format.

ExplanationWhile analyzing a table, DSNTXTB encountered acolumn that has an unexpected name or attribute.




column-numberThe location of the unexpected name or attribute.

expected-formatThe format that is required for the name orattribute.

actual-formatThe format that is used for the name or attribute.


User response1. Query SYSIBM.SYSCOLUMNS, and inspect the

column names and attributes of the table. Forexample, use the following query:

SELECT NAME, COLNO, CASE COLTYPE WHEN 'TIMESTMP' THEN 'TIMESTAMP' ELSE COLTYPE END, LENGTH ,LENGTH2 FROM SYSIBM.SYSCOLUMNS WHERE TBCREATOR = 'schema-name' AND TBNAME = 'table-name' ORDER BY COLNO;

Use the information about SYSIBM.SYSCOLUMNSto help you locate the structural problem.

2. If you suspect that the table might not be anEXPLAIN table, review the list of EXPLAIN tables.Compare your table to the expected table of thesame name. If the table is not an EXPLAIN table,consider renaming it.

3. If the table is an EXPLAIN table, it is not in theexpected format and you must correct thediscrepancy. You can either:

• Alter the table to conform to the format describedfor the table.

• Rename the existing table, create a replacementtable with the appropriate name in the expectedformat, and copy the data from the original tableto the replacement. When you have confirmedthe contents of the replacement table, drop theoriginal table.

Severity8 (error)

DSNT096I WARNING: THE TARGETDATABASE, database-name, ISNOT A UNICODE DATABASE

ExplanationThe target database specified for new Unicode explaintables already exists in Db2 and is not a Unicodedatabase by default.




If you prefer to have the new explain tables created ina Unicode database, change the appropriate targetdatabase parameter to specify either an existingUnicode database or the name of a new one for whichDSNTXTB should generate a CREATE statement. Thenrerun DSNTXTB.


DSNT097I DSNTXTB REQUEST CANCELLEDBECAUSE THE SPECIFIED TARGETrequired-type TABLE SPACE,database-name.tablespace-name,IS AN EXISTING actual-typeTABLE SPACE

ExplanationThe indicated table space already exists in Db2 as adifferent type of table space than is required.

required-typeThe type of table space that was specified as aDSNTXTB input parameter: 4KB page table space,8KB page table space, 16KB page table space, 8KBpage LOB TS, or 32KB page LOB TS.

database-name.tablespace-nameThe table space that was the target of theDSNTXTB request.

actual-typeThe type of the existing table space that isidentified by database-name.tablespace-name:4KB page table space, 8KB page table space, 16KBpage table space, 8KB page LOB TS, 32KB pageLOB TS, or NON-UNICODE.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsyscolumnstable.html


User responseCorrect the DSNTXTB input parameter indicated byrequired-type so that it specifies one of the followingnames:

• An existing, conforming Unicode-encoded tablespace.

• A new table space for which DSNTXTB shouldgenerate a CREATE statement with the requiredattributes.

Severity8 (error)

DSNT098I DSNTXTB HAS GENERATEDSTATEMENTS TO CREATEUNICODE EXPLAIN TABLES FORTHE SPECIFIED SCHEMA IN ANEXISTING TARGET TABLE SPACE,database-name.tablespace-name

ExplanationThe indicated table space already exists in Db2. If thecontrol statements that were generated by thisexecution of DSNTXTB are processed, this table spacewill be used as the target table space for new Unicodeexplain tables.


tablespace-nameThe name of the table space.



If you prefer to have the new explain tables created ina different table space, change the appropriate targettable space parameter to specify either a differentexisting Unicode table space or the name of a new onefor which DSNTXTB should generate a CREATEstatement. Then rerun DSNTXTB.


DSNT099I DSNTXTB HAS GENERATEDSTATEMENTS FOR MIGRATINGTABLE schema-name.table-nameTO UNICODE

ExplanationAn EBCDIC-encoded explain table was found in thespecified schema. One instance of this message isissued for each EBCDIC-encoded explain table.






DSNT101I A VSAM ERROR HAS BEENENCOUNTERED WHILE CSECTDSNTSTR2 WAS READING THEDB2 BSDS VSAM RETURN CODE =return-code, VSAM REASON CODE= reason-code

ExplanationCSECT DSNTSTR2 attempted to read the Db2bootstrap data set (BSDS), and a VSAM error hasoccurred. return-code is a 1-byte VSAM return codeand reason-code is a 1-byte VSAM reason code.

System actionThe start up process continues. However, anyreferences to password-protected system databaseswill cause a 'resource unavailable' error. Any agent-related requests for subsystem database resourceswill result in an SQLCODE -904. Any requests that arenot agent-related for unavailable resources will resultin the following messages:

DSNI001IDSNI005IDSNT415I

DSNI002IDSNI006IDSNT416I

DSNI003IDSNT408IDSNT417I

DSNI004IDSNT414IDSNT500I

Abend X'04E' with reason code X'00E30010' is alsoproduced. However, the error results in a retry. Db2does not terminate, but a dump is produced.



System programmer responseA VSAM error occurred while reading the BSDS recordwith key '200000001'. Either the BSDS record doesnot exist or an I/O error occurred (indicating that therecord is bad). Further information may be obtainedfrom a VSAM diagnostics manual.






.

Related conceptsManagement of the bootstrap data set (Db2Administration Guide)Related informationRecovering from BSDS failures (Db2Administration Guide)-904 (Db2 Codes)00E30010 (Db2 Codes)

DSNT102I DSNTSTR2 - AN INVALIDDATABASE SERVICES BOOTSTRAPRECORD HAS BEENENCOUNTERED

ExplanationCSECT DSNTSTR2 attempted to read the Db2bootstrap data set (BSDS), and an invalid record wasread by the recovery log manager (RLM)subcomponent. This error is an internal Db2 error.

The invalid record is a database services passwordrecord with key '200000001.'

System actionDb2 start-up processing continues.

However, any references to Db2 password-protectedsystem databases cause a resource unavailablecondition. Any agent-related requests for unavailableDb2 subsystem database resources result in anSQLCODE -904. Any requests that are not agent-

related for unavailable resources result in one or moreof the following messages:

• DSNI001I• DSNI002I• DSNI003I• DSNI004I• DSNI005I• DSNI006I• DSNT408I• DSNT414I• DSNT415I• DSNT416I• DSNT417I• DSNT500I

Abend X'04E' with reason code X'00E30010' alsooccurs with message DSNT102I. As a result of thiserror, Db2 tries the operation again. Db2 does notterminate, but produces a dump.


System programmer responseCollect the information that is identified in the problemdetermination section and contact IBM Support.






•

.

Related tasksCollecting diagnostic data (Collecting data)Related referenceDb2 abend completion codes (X'04E' andX'04F) (Db2 Codes)


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_bsdsmanagement.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_bsdsmanagement.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverbsdsfailures.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/trbshoot/src/tpc/db2z_recoverbsdsfailures.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00e30010.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_abendcompletioncodes.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_abendcompletioncodes.html

Related informationDSNI001IRESTART HAS BEEN DEFERRED REASONreason-code TYPE resource-type NAME resouce-nameDSNI002Icsect-name UNABLE TO START OBJECT TYPEobject-type OBJECT NAME object-nameREASON reason-code TYPE resource-type NAMEresource-nameDSNI003Icsect-name UNABLE TO STOP OBJECT TYPEobject-type OBJECT NAME object-nameREASON reason-code TYPE resource-type NAMEresource-nameDSNI004IRESOURCE HAS BEEN STOPPED TYPE resource-type NAME resource-nameDSNI005Icsect-name LPL OR GRECP RECOVERY CANNOTBE DONE FOR function-name - ID = function-idOBJECT TYPE object-type OBJECT NAME object-name REASON reason-code TYPE resource-typeNAME resource-nameDSNI006Icsect-name ASYNCHRONOUS GRECP OR LPLRECOVERY IN PROGRESS FOR function-name -ID function-id TYPE object-type NAME object-nameDSNT408ISQLCODE = -sql-code, explanationDSNT414ISQLERRM = xxxx, SQLCA ERROR MESSAGEINSERTION TEXTDSNT415ISQLERRP = xxxx, SQL PROCEDURE DETECTINGERRORDSNT416ISQLERRD = field-1, field-2, field-3, field-4,field-5, field-6 SQL DIAGNOSTIC INFORMATIONDSNT417ISQLWARNn-n SQL WARNINGSDSNT500Icsect-name RESOURCE UNAVAILABLE REASONreason-code TYPE resource-type NAMEresource-name-904 (Db2 Codes)00E30010 (Db2 Codes)

DSNT103I THE CURRENTLY LOADEDDSN6SPRM IS NOT THE MVS/XAVERSION

ExplanationA -START DB2 PARM=xxxxxxxx was issued where'xxxxxxxx' is the version of the system parameterCSECTs. Db2 executes in a MVS/XA environment andwill not execute in any other environment.

System actionThe message DSNV086E is generated with a reasoncode of X'00E30008'. Db2 is terminated with abendcode X'04F'.


System programmer responseRestart Db2 with a -START DB2 PARM= command,where the parameter block that follows the 'PARM='parameter specifies an MVS/XA version of the Db2subsystem parameters.






• Listing of DSNZPARM module used.

.

DSNT104I THE CURRENTLY LOADEDDSN6SPRM IS NOT THE MVS/370VERSION

ExplanationA -START DB2 PARM=xxxxxxxx was issued, where'xxxxxxxx' is the version of the system parameterCSECTs. Db2 executes in an MVS/370 environmentand does not execute in any other environment.

System actionMessage DSNV086E is generated with reason codeX'00E30009'. Db2 is terminated with abend codeX'04F'.



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/00e30010.html


System programmer responseRestart Db2 with a -START DB2 PARM= command,where the parameter block that follows the PARM=parameter specifies an MVS/370 version of the Db2subsystem parameters.







.

DSNT105I THE LOADED DSN6SPRM CSECT ISOBSOLETE. PLEASE REASSEMBLETHE DSN6SPRM CSECT ANDRELINKEDIT THE DSNZPARMLOAD MODULE.

ExplanationDSNTSTR2 loaded an out-of-date system parameterCSECT DSN6SPRM. This error can only occur if codemaintenance has been applied and CSECT DSN6SPRMhas not been reassembled. This CSECT is contained inthe load module specified in the 'PARM=' parameter ofthe -START DB2 command.



System programmer responseReassemble DSN6SPRM, and relink-edit theDSNZPARM load module. This is done by resubmitting

the installation job stream, DSNTIJUZ, that built theload module that is named following the 'PARM='parameter of the -START DB2 command.







.

DSNT106I THE LOADED DSN6SYSP CSECT ISOBSOLETE. PLEASE REASSEMBLETHE DSN6SYSP CSECT ANDRELINKEDIT THE DSNZPARMLOAD MODULE.

ExplanationDSNTSTR2 loaded an out-of-date system parameterCSECT DSN6SYSP. This error can only occur if codemaintenance has been applied and CSECT DSN6SYSPhas not been reassembled. This CSECT is contained inthe load module specified in the 'PARM=' parameter ofthe -START DB2 command.



System programmer responseReassemble DSN6SYSP, and relink-edit theDSNZPARM load module. This is done by resubmittingthe installation job stream, DSNTIJUZ, that built theload module that is named following the 'PARM='parameter of the -START DB2 command.








DSNT107I INVALID AMODE OR RMODEATTRIBUTE FOUND FOR LOADMODULE module-name

ExplanationDuring Db2 startup, the service controller establishesthe addressability to the Db2 database servicesfunctional recovery and the emergency shutdownroutines. Two load modules, DSNTF, and DSNTLCLE,are loaded into CSA. In the MVS/XA environment,DSNTLCLE must be link-edited with attributesAMODE(24) and RMODE(ANY). At least one of themodules did not have the correct addressing attributewhen it was loaded. 'module-name' in the errormessage is the name of the first load module that hasan invalid addressing mode.

System actionDb2 database services start up is terminated.


System programmer responseVerify that all installation and maintenance activitiesagainst these modules were executed using SMP.Verify that the JCLIN for SMP includes the correctAMODE and RMODE control statements, and that thelinkage editor provided with the Data Facility Product(DFP) was invoked by SMP for the link edits. Correctthe procedure or JCL which caused the error and rerunthe necessary SMP jobs.

Problem determinationA Db2 dump was requested to an MVS/XA SYS1.DUMPdata set.

The MVS service aid AMBLIST provides linkage editormodule attributes in the summary section of theLISTLOAD function output.

DSNT108I DB2 HAS DETECTED ADIFFERENCE BETWEEN THERECORDED SYSTEM CCSIDS ANDTHE CCSIDS SPECIFIED BYDSNHDECP

ExplanationDuring Db2 startup, Db2 detected a differencebetween the CCSIDs recorded in the BSDS and theCCSIDs specified by the version of DSNHDECP, or theuser-specified application defaults module, that wasloaded during startup. Db2 startup terminated to avoidpotential data corruption issues.



System programmer responseDetermine the reason for the mismatch between theCCSIDs in the BSDS and the CCSIDs specified by thedsnhdecp module that was loaded during startup.Possible reasons for a mismatch include that theprocedure used to start Db2 might have incorrectlibrary concatenations, or, the copy of the dsnhdecpmodule that was loaded was incorrectly copied to thelibraries specified by the Db2 startup procedure.

Correct the mismatch. If IBM support directs you, youcan use the change log inventory (DSNJU003) utilitywith the DELETE CCSIDS clause to delete the CCSIDsthat are specified in the in the BSDS. Important: Donot attempt to delete the CCSIDs in the BSDS unlessIBM support instructs you.

Related conceptsApplication defaults parameters (Db2Installation and Migration)Application defaults module name at start (Db2Administration Guide)Related tasksSpecifying CCSIDs in Db2 (Db2Internationalization Guide)

DSNT109I DB2 HAS DETECTED AN INVALIDCCSID IN THE CCSID(S)SPECIFIED FOR ENCODINGSCHEME encoding-scheme BYDSNHDECP




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/admin/src/tpc/db2z_appmodnameatstart.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/char/src/tpc/db2z_specifyccsiddb2.html


ExplanationThe version of DSNHDECP, or the user-specifiedapplication defaults module, that was loaded duringDb2 startup has invalid CCSIDs for the encoding-scheme encoding scheme. Db2 startup terminated toavoid potential data corruption issues.



System programmer responseIf the dsnhdecp value for MIXED is NO, the specifiedCCSIDs must be SBCS CCSIDs. You can find theseCCSIDs in the table entitled "Single-byte codedcharacter set identifiers (CCSIDs)".

If the dsnhdecp value for MIXED is YES, then you mustselect ASCII MIXED from the table entitled "ASCIIdouble-byte coded character set identifiers (CCSIDs)",and you must select EBCDIC MIXED CCSIDs from thetable entitled "EBCDIC double-byte coded characterset identifiers (CCSIDs)".

Unicode CCSID values are pre-filled and you shouldnot change them.

Related conceptsApplication defaults parameters (Db2Installation and Migration)Application defaults module name at start (Db2Administration Guide)Character conversion (Introduction to Db2 forz/OS)Related tasksSpecifying CCSIDs in Db2 (Db2Internationalization Guide)

DSNT200I type bind-type FOR PLAN plan-idSUCCESSFUL

ExplanationA BIND, REBIND or FREE PLAN subcommand hascompleted successfully.type

Indicates that a test bind was in progress. A testbind means that no plan name was specified. Thetoken is omitted if a normal BIND PLAN wasprocessed.

bind-typeType of bind subcommand: BIND, REBIND, orFREE.

plan-idName of application plan specified in thesubcommand.

System actionThe plan was successfully bound, rebound, or freed.

DSNT201I type bind-type FOR PLAN plan-idNOT SUCCESSFUL

ExplanationErrors have been detected during the processing of theindicated BIND, REBIND, or FREE PLAN subcommand.type

Indicates that a test bind was in progress. A testbind means that no plan name was specified. Thetoken is omitted if a normal BIND PLAN wasprocessed.

bind-typeType of bind subcommand: BIND, REBIND, orFREE.


System actionThe BIND, REBIND, or FREE PLAN was not performed.

System programmer responseSee other messages issued to determine the error thatcaused the bind subcommand to terminateunsuccessfully.

DSNT202I MESSAGE LIMIT EXCEEDED

ExplanationA fixed amount of space exists in which to generatebind subcommand messages. This message says thatthe bind subcommand generated more messages thanwill fit in that space.

System actionFor bind subcommands that affect a single plan, thebind subcommand process continues. However, noother messages are generated except for messageDSNT200I or DSNT201I. For bind subcommands thataffect more than one plan, the bind subcommand






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_characterconversion.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/intro/src/tpc/db2z_characterconversion.html



process terminates and no other messages aregenerated.

System programmer responseThe 'FLAG' parameter of the bind subcommand can beused to limit the types of messages that are generated.

DSNT203I bind-type WARNING FOR object-type object-name DBRMS ARECONVERTED INTO PACKAGESBEFORE bind-typeobject-typeobject-name.

ExplanationAn attempt was made to bind DBRMs directly into aplan or to rebind a plan with DBRMs that were alreadybound.

bind-typeThe type of BIND subcommand, such as BIND orREBIND.

object-typeThe type of object, such as PLAN.

object-nameThe name of the application plan.

This message can be caused by using the MEMBERoption when binding a plan or by rebinding a plan withDBRMs that were bound in an earlier version of Db2.

System actionThe bind process continues and the conversion iscompleted.


Severity4 (warning)

DSNT204I bind-type WARNING FOR object-type object-name, option IS option-status, substitute-option WILL BEUSED.

ExplanationA BIND subcommand was issued with an invalidoption.

bind-typeThe type of BIND subcommand, such as REBIND.

object-typeThe type of object, such as PLAN or PACKAGE.


optionThe unsupported BIND option.

option-statusThe problem with option. Possible values are:INVALID

The BIND option is not valid in the contextwhere it is used.

NOT USEDThe BIND option syntax is valid, but the optionhas no effect.

substitute-optionThe BIND option that was used instead of option.

This message can be caused by the use of adeprecated option.

System actionThe bind process continues, using the option that isindicated by substitute-option.


Severity4 (warning)

Related referenceBIND and REBIND options for packages, plans,and services (Db2 Commands)

DSNT205I name IS A DUPLICATE name-type,IT WILL BE USED ONLY ONCE

ExplanationName 'name' has been specified more than once in alist of names.name

Name that was specified more than once.name-type

Indicates the type of list in which the name wasduplicated.

• MEMBER NAME - List of DBRM Members• PLAN-ID - List of plan IDs• SYSTEM NAME - List of system connection

names on a DISABLE or ENABLE list.• PACKAGE NAME - List of package IDs




System actionDuplicates are removed from 'name-type' list and thebind process continues.

System programmer responseVerify the list that contains the duplicate. If the error isonly in entering a name incorrectly, which happens toduplicate another entry, enter the name correctly andreissue the bind statement. If the entry is really aduplicate, no action is required.

DSNT206I bind-type WARNING FOR object-type object-name DEFAULTCOLLECTION ID:DSN_DEFAULT_COLLID_object-name IS USED IN THE PACKAGELIST, POSSIBLE DBRMSORIGINALLY BOUND WITH THEbind-type HAVE BEEN CONVERTEDINTO PACKAGES DURINGEXECUTING THE object-typePRIOR TO bind-type

ExplanationThe default collection ID(DSN_DEFAULT_COLLID_object-name) has beendetected in the package list of the plan during therebind process.

The default collection ID is the result of an automaticconversion from DBRMs to packages within a plan.This message is issued when such a plan is reboundagain. This condition typically happens when the plancontains DBRMs that were directly bound, but that theDBRMs have been converted into packages. Thisconversion usually happens during an attempt to usethe plan in a newer release of Db2 than the one inwhich it was created.

bind-typeThe type of BIND subcommand, such as REBIND.

object-typeThe type of object, such as PLAN.


System actionThe rebind process continues and the plan is reboundwith the package list.


Severity4 (warning)

DSNT207I PROGRAM program-name WITHMARK release-dependency-markFAILED BECAUSE IT DEPENDS ONFUNCTIONS OF THE RELEASEFROM WHICH FALL BACK HASOCCURRED

ExplanationProgram 'program-name' depends on a function ofDb2 that is not supported by the current activerelease.program-name

Name of the application program.release-dependency-mark

A one-character mark showing the oldest Db2release supporting this program.

System actionThe bind operation for this plan or package is notperformed.

System programmer responseWarn users not to use plans or packages containingthis program until the Db2 subsystem has beenremigrated to the newer release.

User responseThe program cannot be used until the Db2 subsystemis remigrated to the newer release. Notify the systemprogrammer.

DSNT208I PROGRAM program-namePRECOMPILED WITH INCORRECTLEVEL FOR THIS RELEASE

ExplanationProgram 'program-name' was precompiled under arelease not supported by the current level of Db2, orthe contents of the DBRM have been modified after theprecompilation phase.

System actionThe BIND operation was not performed.

User responsePrecompile the named program again using thecurrent precompiler. Reissue the BIND command.


Problem determinationIf the application program was precompiled at anappropriate release, and the problem persists, collectthe following diagnostic items:

• Hexadecimal print of the first record of the failingDBRM.

• Listing from the precompile job that generated theDBRM.

• Output from the BIND attempt.

.

DSNT209I bind-type FOR PLAN plan-id WITHMARK release-dependency-markFAILED BECAUSE PLAN DEPENDSON FUNCTIONS OF THE RELEASEFROM WHICH FALL BACK HASOCCURRED.

ExplanationPlan 'plan-id' depends on a function of Db2 which isnot supported by the currently active release.bind-type

REBINDplan-id

Name of the application planrelease-dependency-mark

A one-character mark showing the oldest releaseof Db2 which can support this plan. The releasedependency mark for the plan is kept in theIBMREQD columns in the Db2 catalog inSYSIBM.SYSPLAN.

System actionThe REBIND operation for this plan is not performed.


System programmer responseWarn users not to use the plan until the Db2subsystem has been remigrated to the newer release.

User responseThe plan cannot be used until the Db2 subsystem isremigrated to the newer release.

DSNT210I bind-type AUTHORIZATION ERRORUSING authorization-idAUTHORITY PLAN=plan-idPRIVILEGE=privilege

ExplanationThe indicated authorization ID does not have theindicated privilege and therefore cannot invoke theindicated BIND subcommand against the indicatedapplication plan. If the access control authorizationexit is active and the AUTHEXIT_CHECK subsystemparameter is set to DB2, this error might occur if ACEEcannot be created for the indicated authorization ID.bind-type

Type of BIND subcommand: BIND, REBIND, FREE.authorization ID

Authorization ID of the plan owner. Note: If you areusing a trusted context, the token auth-id mightreturn a role instead of an authorization ID. A roleis returned, if a role was in effect and theauthorization checking is performed against therole rather than the authorization ID of the session,when the condition was encountered. The role isreturned in the following format as a single token:ROLE: role-name.

plan-idApplication plan specified in the BINDsubcommand.

privilegeMissing privilege: BIND, BINDADD

System actionThe BIND, REBIND, or FREE operation for 'plan-id' isnot performed.

System programmer responseIf the indicated privilege is BINDADD, then theprivilege to invoke the BIND subcommand with theACTION(ADD) option must be granted to the indicatedauthorization ID. If the indicated privilege is BIND, theprivilege to invoke a BIND subcommand against theindicated application plan must be granted to theindicated authorization ID.

If you use the access control authorization exit, ensurethat the indicated authorization ID is defined in RACFand granted the indicated privilege in RACF.

DSNT211I REBIND FOR PLAN plan-id FAILEDBECAUSE IBMREQD OF ibmreqd ISINVALID

ExplanationThe IBMREQD column of the SYSIBM.SYSPLAN catalogtable for the named plan contains an unrecognizablecharacter.


System actionThe REBIND operation for the plan was not performed.

System programmer responseYou must do a BIND ACTION(REPLACE) for this plan.

DSNT212I bind-type AUTHORIZATION IDauth-id IN THE OWNER KEYWORDIS INVALID

ExplanationThe authorization ID specified in the OWNER keywordof the BIND or REBIND subcommand is invalid.Specifying an owner that is not the primaryauthorization ID or one of the secondary IDs of theprocess requires additional authority.

bind-typeType of bind subcommand: BIND or REBIND

auth-idThe authorization ID specified as owner.

If you are using a trusted context, the token auth-id might return a role instead of an authorizationID. A role is returned, if a role was in effect and theauthorization checking is performed against therole rather than the authorization ID of the session,when the condition was encountered. The role isreturned in the following format as a single token:ROLE: role-name.

System actionThe BIND or REBIND subcommand is not executed.

System programmer responseRerun the subcommand and specify a validauthorization ID for the OWNER bind option. Ifnecessary, add the required authorization ID for thisuser to the security system.

Related tasksEstablishing or changing plan or packageownership (Managing Security)Binding application packages and plans (Db2Application programming and SQL)Related referenceOWNER bind option (Db2 Commands)Privileges required for handling plans andpackages (Managing Security)Related informationAbout Db2 and related commands (Db2Commands)

DSNT213I THE DCB BLOCK SIZE OF THEINPUT DBRM LIBRARY IS INVALID

ExplanationAn invalid DCB block size is specified for the DBRMlibrary of the BIND subcommand.

System programmer responseCorrect the DCB block size of the DBRM library, andreissue the BIND subcommand.

DSNT214I I/O ERROR ON DBRM LIBRARYDBRM MEMBER= dbrm-nameDBRM LIBRARY= dbrm-library-name xxxxxx

ExplanationAn I/O error occurred during execution of a BINDsubcommand when the database request module(DBRM) was read.dbrm-name

The name of the DBRM or zFS file that isassociated with the error.

dbrm-library-nameThe partitioned data set or the absolute path of azFS file that is associated with the error.

xxxxxxA portion of the message text that was generatedby the SYNADAF macro instruction to describe thepermanent I/O error. This text might containinformation such as the job name, step name, unitaddress, device type, DD name, the operation thatwas attempted, and a description of the error.

System actionNo application plan is created.

System programmer responseDetermine if an incorrect file name was specified in theLIBRARY parameter of the BIND subcommand, or anincorrect data set name was specified for theDBRMLIB DD statement. Check correctly specifieddata sets for I/O errors or modified DCB attributes.

DSNT215I csect-name bind-type bind-subtypeFOR PACKAGE = package-nameFAILED BECAUSE AT LEAST ONEBIND OPTION IS NOT ALLOWEDFOR A package-type PACKAGE


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_changeplanowner.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_changeplanowner.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_bindapp.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptowner.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_privilege4plan.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_privilege4plan.html



ExplanationThe BIND or REBIND subcommand has beensubmitted with an invalid combination of bind options.The message tokens provides the followinginformation:csect-name



bind-subtypeType of bind subcommand: COPY, DEPLOY, orBLANK.

package-nameName of the package in the format: location-id.collection-id.package-id(version-id).package-type

package-typeType of package:

• PROCEDURE• NATIVE SQL PL PROCEDURE• TRIGGER• FUNCTION• REST SERVICE

.

System actionThe bind fails.

User responseRemove the incompatible bind options and reissue thecommand.

Related referenceBIND PACKAGE (DSN) (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)REBIND PLAN (DSN) (Db2 Commands)Related informationAbout Db2 and related commands (Db2Commands)

DSNT216I REBIND FOR PACKAGE = package-name FAILED BECAUSE AT LEASTONE BIND OPTION SPECIFIEDCANNOT BE CHANGED INCONJUNCTION WITH PLANMGMT.

ExplanationAn attempt was made to rebind a package using thePLANMGMT option, but a new value was indicated fora bind option that cannot be changed from its previousvalue.

package-nameThe name of the package.

When PLANMGMT is specified, the following bindoptions cannot be changed from their previous values.

• OWNER• QUALIFIER• ENABLE• DISABLE• PATH• PATHDEFAULT• IMMEDWRITE


Operator responseRemove the conflicting REBIND options and re-invokethe command.

Related tasksSaving and switching to previous access paths(Db2 Performance)

DSNT217I REBIND SWITCH FOR PACKAGE =package_name FAILED BECAUSETHE PREVIOUS OR ORIGINALCOPY DOES NOT EXIST.

ExplanationAn attempt was made to revert to a non-existentPREVIOUS or ORIGINAL copy of a package.


DSNT218I REBIND FOR PACKAGE =package_name FAILED BECAUSESWITCH CANNOT BE SPECIFIEDWITH ANY OTHER REBINDOPTIONS








https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_accesspathswitch.html


ExplanationWhen attempting to SWITCH to a PREVIOUS orORIGINAL copy of a package, no other bind optionscan be specified.


Operator responseRemove the conflicting bind options and issue thecommand again.

Related tasksSaving and switching to previous access paths(Db2 Performance)Related referenceSWITCH bind option (Db2 Commands)

DSNT219I REBIND FOR PACKAGE =package_name SUCCEEDED BUT APREVIOUS AND/OR ORIGINALPACKAGE COPY WAS NOTCREATED/REPLACED BECAUSETHE CURRENT PACKAGE COPYWAS INVALID.

ExplanationWhen a REBIND PACKAGE command is invoked on aninvalid package, any PLANMGMT= BASIC orPLANMGMT=EXTENDED options are ignored. Db2rebinds the package successfully. However, anypreviously existing or original copies are not modified.



DSNT220I BIND ADD ERROR USING auth-idAUTHORITY PLAN plan-idALREADY EXISTS

ExplanationAn attempt was made to use the BIND subcommandwith the 'ACTION(ADD)' option that specified a 'plan-id' that already exists.auth-id

Authorization ID of the owner of the plan.Attention: If you are using a trusted context, thetoken auth-id might return a role instead of an

authorization ID. A role is returned, if a role was ineffect and the authorization checking is performedagainst the role rather than the authorization ID ofthe session, when the condition was encountered.The role is returned in the following format as asingle token: ROLE: role-name.

plan-idApplication plan specified in the BINDsubcommand.

System actionNo application plan is created.

System programmer responseCheck the SYSIBM.SYSPLAN catalog table for namesof existing application plans. Reinvoke the BINDsubcommand with a 'plan-id' that is not in use.

DSNT221I bind-type ERROR USING auth-idAUTHORITY PLAN plan-id DOESNOT EXIST

ExplanationThe indicated bind subcommand was issued againstan application plan that does not exist. The individualvariable fields contain:bind-type

Type of bind subcommand: REBIND or FREE.auth-id

Authorization ID of the plan owner.plan-id

Application plan specified in the BINDsubcommand.

System programmer responseCheck the SYSPLAN catalog table for the correct 'plan-id' to use.

DSNT222I csect-name bind-type WARNINGFOR object-type = object-name USEOF OPTHINT RESULTS IN count-1STATEMENTS WHERE OPTHINTFULLY APPLIED count-2STATEMENTS WHERE OPTHINTNOT APPLIED OR PARTIALLYAPPLIED count-3 STATEMENTSWHERE OPTHINT IS NOT FOUND

ExplanationThe OPTHINT option of Bind or Rebind was specified.This message gives counts of the number of




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptswitch.html

statements where a hint was fully applied, not fullyapplied, or not found.csect-name

The name of the csect from which the messagewas issued.

bind-typeType of BIND subcommand: BIND or REBIND.

object-typePLAN or PACKAGE

object-nameIf object-type is PLAN, object-name is the name ofthe plan.

If object-type is PACKAGE, object-name is thename of the package in the format 'location-id.collection-id.package-id'.

count 1The number of statements where hints werefound, and all hints found were successfullyapplied.

count 2The number of statements where hints were foundand at least one of those hints could not besuccessfully applied.

count 3The number of statements where there were nomatching optimization hints found.


Programmer responseExamine the counts to ensure that the specifiedoptimization hints were applied to the intendedstatements. Refer to SQL codes +394 and +395 formore information about individual statements.

DSNT223I csect-name bind-type WARNINGFOR object-type = object-name USEOF OPTHINT IS DISALLOWED BY ADB2 SUBSYSTEM PARAMETER.THE DEFAULT OPTHINT VALUE ISUSED.

ExplanationThe Db2 subsystem parameters have not beenconfigured to enable the use of OPTHINT in the bind-type subcommand. The default OPTHINT value of allblanks is used.bind-type

Type of BIND subcommand: BIND or REBIND.



If object-type is PACKAGE, object-name is thename of the package in the format 'location-id.collection-id.package-id'.

System actionProcessing continues normally using the defaultOPTHINT value.

System programmer responseEnable the use of OPTHINT by changing the value ofOPTIMIZATION HINTS on the Db2 Installation panel,DSNTIP8.

If, after further consideration, you do not want to useOPTHINT, remove OPTHINT from the bind-typesubcommand or set the value to all blanks.

DSNT224I csect-name bind-type ERROR FORobject-type object-name CCSID =ccsid IS INVALID FOR ENCODINGSCHEME = scheme

ExplanationThe system does not have a valid CCSID defined forthe specified encoding scheme, or the specified CCSIDis not defined on the system.bind-type

Type of bind subcommand: BIND or REBIND.object-type

PLAN or PACKAGE.object-name

If object-type is PLAN, object-name is the name ofthe application. Otherwise, it is the name of thepackage in 'location.collection.package' format.

schemeThe encoding scheme specified in the ENCODINGbind option on the subcommand or defaulted fromthe system default Application Encoding Scheme.If scheme is UNKNOWN, then the CCSID valuespecified in the ENCODING bind option ordefaulted from the system default ApplicationEncoding Scheme is not defined, and therefore theencoding scheme is not known.

ccsidThe numeric CCSID corresponding to the specifiedccsid-type.


System actionThe bind-type operation is not performed

System programmer responseIf the bind option ENCODING was not specified, andinstead the value for ENCODING was defaulted fromthe system default Application Encoding Scheme,verify the Application Encoding Scheme is set to adefined CCSID.

If the value specified for the ENCODING option wasASCII, EBCDIC or UNICODE, verify the correspondingsubsystem parameters on the installation panelDSNTIPF has been set to a defined CCSID. Otherwise,inform the user of the correct CCSID.

User responseVerify that the correct encoding scheme was specifiedin the ENCODING bind option on the bind-typesubcommand. If correct, see System ProgrammerResponse and contact the System Programmer. Ifincorrect, specify the correct scheme in theENCODING option and reissue the bind-typesubcommand.

Severity8 (error)

Related conceptsIntroduction to character conversion (Db2Internationalization Guide)Related tasksSetting up Db2 to ensure that it interpretscharacters correctly (Db2 InternationalizationGuide)Related referenceDSNTIPF: Application programming defaultspanel 1 (Db2 Installation and Migration)ENCODING bind option (Db2 Commands)

DSNT225I bind-type ERROR FOR object-typeobject-name, bind-option IS NOTSUPPORTED.

ExplanationThe BIND or REBIND command specified invalidoptions.

bind-typeThey type of bind request: BIND, BIND COPY, orREBIND.


object-nameThe name of the application plan or the package.

bind-optionThe unsupported bind option.

System actionThe bind process fails.

User responseCorrect the bind option, and rerun the BIND or REBINDcommand.

Problem determinationOne condition under which this message is issued iswhen DBPROTOCOL(PRIVATE) is either specified orimplied, and private protocol is not allowed.

Related referenceBIND and REBIND options for packages, plans,and services (Db2 Commands)

DSNT226I bind-type WARNING FOR object-type object-name. bind-optionOPTION IS NOT RECOMMENDEDWHEN BINDING PLANS ORPACKAGES

ExplanationThe indicated subcommand was issued with a bindoption that is deprecated and no longer recommendedfor use.bind-type

Type of bind subcommand: BIND COPY, BINDREPLACE, REBIND, BIND PLAN, or REBIND PLAN.


object-nameThe name of the application plan or the package.

bind-optionThe bind option that is deprecated and expected tobe unsupported in the future.

System actionThe bind process continues.

User responseIf DBPROTOCOL(PRIVATE) was explicitly specified forthe bind-option that is not recommended, then Db2issues a warning during the bind-type operation onobject-type. To avoid this warning, rerun the bind-type


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/char/src/tpc/db2z_introcharconv.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/char/src/tpc/db2z_introcharconv.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/char/src/tpc/db2z_setupdb2charconv.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntipf.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_dsntipf.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_bindoptencoding.html



operation on object-type specifyingDBPROTOCOL(DRDA) or allow the bind-type operationto default.

Related referenceDeprecated function in Db2 11 (Db2 for z/OSWhat's New?)BIND and REBIND options for packages, plans,and services (Db2 Commands)

DSNT227I bind-action WARNING FOR SQLPROCEDURE PACKAGE: location-name.collection-id.package-id.(version-id) THE TARGET SERVERWAS NOT ABLE TO RESOLVESTRUCTURE INFORMATION INTHE SOURCE PACKAGE.ADDITIONAL AUTOMATICREGENERATION PROCESSINGWILL OCCUR ON THE TARGETSERVER.

ExplanationA stored procedure was created in one version of Db2and bound for use on an earlier version. Somestructural information in the new package must beresolved by the target server during the bind process.If the BIND request succeeded, you can use theresulting package on the earlier version.

bind-actionThe requested BIND action, such as BIND DEPLOY.

location-name.collection-id.package-id.(version-id)Identifies the package that was bound.


User responseNo action is required on the Db2 11 subsystem. Whenyou execute the package on the target server, monitorthe console output for SQLCODE -904 which indicatesthat the automatic processing was unsuccessful.

Related tasksDeploying a native SQL procedure to anotherDb2 for z/OS server (Db2 Applicationprogramming and SQL)Related referenceBIND PACKAGE (DSN) (Db2 Commands)BIND and REBIND options for packages, plans,and services (Db2 Commands)

DSNT228I BIND ERROR, ATTEMPTING TOREPLACE PACKAGE =

package_name WITH version=(version2) BUT THIS VERSIONALREADY EXISTS

ExplanationAn attempt is made to create a version of a packagethat already exists. The version specified in theREPLVER keyword is different from the versionspecified for the precompile. The version specified forthe precompile already exists in the catalog. Thecombination of 'location.collection.package.version'must be unique in the SYSIBM.SYSPACKAGE catalogtable. A common mistake is that the user may believethat the version he is creating is the one specified inthe REPLVER keyword. This is not the case. Theversion specified in the REPLVER keyword is the nameof the version being replaced. The version that will becreated is the version that was given to the programwhen it was precompiled.package_name

Fully qualified package nameversion2

Version-id of package that is to be created

System actionThe bind will fail.

System programmer responseThere are two approaches to solve this problem. Thefirst is to re-precompile the program with a newversion name and re-issue the original BINDsubcommand. The other approach is not to do theprecompile but re-issue the BIND subcommandwithout the REPLVER parameter.

DSNT229I BIND ERROR, ATTEMPTING TOREPLACE PACKAGE = package-name THERE ARE ENABLE ORDISABLE ENTRIES CURRENTLYASSOCIATED WITH THE PACKAGE

ExplanationThe BIND subcommand was issued to replace apackage that has ENABLE or DISABLE entries currentlyassociated with the package. The individual variablefields contain:package-name

Name of the package (location.collection.package)

System actionPackage not bound.






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_deploynativespotherserver.html






System programmer responseFREE the package first and then BIND the package.

DSNT230I BIND DBRM MEMBER NAMEERROR USING auth-id AUTHORITYobject-type = object-name MEMBERdbrm-name NOT FOUND IN PDSSEARCH ORDER

ExplanationThe indicated 'dbrm-name' was not found in thesearch order in the PDSs specified on the BIND PLANor BIND PACKAGE subcommand.auth-id

Authorization ID of the plan or package owner.Attention: If you are using a trusted context, thetoken auth-id might return a role instead of anauthorization ID. A role is returned, if a role was ineffect and the authorization checking is performedagainst the role rather than the authorization ID ofthe session, when the condition was encountered.The role is returned in the following format as asingle token: ROLE: role-name.

object-typeThe type of object being bound: PLAN or PACKAGE

object-nameIf 'object-type' is PLAN, 'object-name' is the nameof the application plan. Otherwise, it is the name ofthe package in 'location.collection.package'format.

dbrm-nameMember name of the DBRM that was not found.

System actionThe bind is unsuccessful.

System programmer responseDetermine if an incorrect 'dbrm-member-name' or PDSwas specified. Reinvoke the BIND subcommandspecifying the correct names.

DSNT231I BIND DBRM ERROR USING auth-idAUTHORITY object-type = object-name DBRM dbrm-name IS IN ANINCONSISTENT STATE

ExplanationThe contents of a DBRM have been modified after theprecompilation process, or the DBRM containsincorrect information in the header.

auth-idAuthorization ID of the invoker of the BINDsubcommand. Attention: If you are using a trustedcontext, the token auth-id might return a roleinstead of an authorization ID. A role is returned, ifa role was in effect and the authorization checkingis performed against the role rather than theauthorization ID of the session, when the conditionwas encountered. The role is returned in thefollowing format as a single token: ROLE: role-name.

object-typeThe type of object being bound: PLAN or PACKAGE


dbrm-nameName of the DBRM that is in error.

System actionThe bind is unsuccessful.

System programmer responsePrecompile the application program associated withthe indicated DBRM. Reinvoke the BIND subcommand.

DSNT232I SUCCESSFUL bind-type FORPACKAGE = package-name

ExplanationA BIND, REBIND or FREE PACKAGE subcommand hascompleted successfully.bind-type

Type of bind subcommand: BIND, REBIND, orFREE

package-nameName of the package in the following format:'location.collection.package.(version)'

System actionThe package was successfully bound, rebound, orfreed.

DSNT233I UNSUCCESSFUL bind-type FORPACKAGE = package-name

ExplanationErrors have been detected during the processing of theindicated BIND, REBIND, or FREE PACKAGEsubcommand.


bind-typeType of bind subcommand: BIND, REBIND, orFREE


System actionThe indicated package was not bound, rebound, orfreed.

System programmer responseSee other messages issued to determine the error thatcaused the subcommand to terminate unsuccessfully.

DSNT234I MESSAGE LIMIT EXCEEDED

ExplanationA fixed amount of space exists in which to generatebind subcommand messages. This message says thatthe bind subcommand generated more messages thanwill fit in that space.

System actionFor bind subcommands that affect a single package orservice, the bind subcommand process continues.However, no other messages are generated except forcompletion message DSNT232I or DSNT233I orcompletion message DSNT276I or DSNT277I forservices. For bind subcommands that affect more thanone package or service, the bind subcommand processterminates and no other messages are generated.

System programmer responseThe 'FLAG' parameter of the bind subcommand maybe used to limit the types of messages that aregenerated.

DSNT235I csect-name bind-typeAUTHORIZATION ERROR USINGauth-id AUTHORITY PACKAGE =package-name PRIVILEGE =privilege

ExplanationThe authorization ID given does not have the privilegeindicated and cannot invoke the bind subcommand onthe named package. If the access control authorizationexit is active and the AUTHEXIT_CHECK subsystemparameter is set to DB2, this error might occur if ACEEcannot be created for the indicated authorization ID.


auth-idAuthorization ID of the invoker of the BINDsubcommand. Attention: If you are using a trustedcontext, the token auth-id might return a roleinstead of an authorization ID. A role is returned, ifa role was in effect and the authorization checkingis performed against the role rather than theauthorization ID of the session, when the conditionwas encountered. The role is returned in thefollowing format as a single token: ROLE: role-name.


privilegeName of the privilege not held:BINDADD or BINDADD *

The authority to create a new package usingBIND with the ADD option.

BINDThe authority to BIND (REPLACE) or REBIND apackage.

BIND *The authority to add a new version of anexisting package using BIND with the ADDoption.

FREEThere is no FREE privilege, but the user needsthe proper authority to free the package.

COPYThe authority to COPY from the indicatedpackage.

CREATE IN or CREATE IN *The authority to create a package in theindicated collection.

A blank and asterisk ( *) in the privilege values'BINDADD *', 'BIND *', and 'CREATE IN *' in themessage indicates that the BINDNV subsystemparameter has the value BIND. When ' *' does notappear in these privilege values, the BINDNVsubsystem parameter has the value BINDADD.

The BINDNV subsystem parameter affects theauthorization required to add a new package or a newversion of an existing package to a collection.

System actionThe indicated package is not bound, rebound, or freed.


System programmer responseYou must grant the indicated privilege to theauthorization ID of the package owner. If you use theaccess control authorization exit, ensure that theindicated authorization ID is defined in RACF andgranted the indicated privilege in RACF.

Related conceptsAccess control authorization exit routine(Managing Security)Related tasksBinding application packages and plans (Db2Application programming and SQL)Related referenceBIND NEW PACKAGE field (BINDNV subsystemparameter) (Db2 Installation and Migration)Explicit package privileges (Managing Security)

DSNT236I REBIND FOR PACKAGE package-name FAILED BECAUSE IBMREQDOF ibmreqd IS INVALID

ExplanationThe IBMREQD column of the SYSIBM.SYSPACKAGEcatalog table for the named package contains anunrecognizable character. This usually means that thepackage depends on a function of Db2 which is notsupported by the currently active release.


System actionThe package was not rebound.

System programmer responseWarn users not to use the package until the Db2subsystem is remigrated to the newer release.

DSNT237I csect-name BIND sub-type ERRORUSING auth-id AUTHORITYPACKAGE = package-nameALREADY EXISTS

ExplanationAn attempt is made to add a package that alreadyexists. The combination of'location.collection.package.version' must be unique inthe SYSIBM.SYSPACKAGE table. In addition, thecombination of'location.collection.package.consistency-token' mustbe unique.

sub-typeThe sub-type can have the values: COPY, ADD orREPLACE.

auth-idAuthorization ID of the owner of the package.Attention: If you are using a trusted context, thetoken auth-id might return a role instead of anauthorization ID. A role is returned, if a role was ineffect and the authorization checking is performedagainst the role rather than the authorization ID ofthe session, when the condition was encountered.The role is returned in the following format as asingle token: ROLE: role-name.


System actionNo package is created.

System programmer responseCheck the SYSIBM.SYSPACKAGE catalog table fornames of existing application packages. Re-invoke theBIND subcommand with a'location.collection.package.version' that is not in use.

DSNT238I bind-type error-type USING auth-idAUTHORITY PACKAGE = package-name DOES NOT EXIST

ExplanationThe indicated subcommand was issued against apackage that does not exist. The individual variablefields contain:bind-type

Type of bind subcommand (BIND COPY | BINDREPLACE | REBIND | FREE| BIND PLAN | REBINDPLAN | DROP PACKAGE). If BIND or REBIND PLANis specified, the package-name refers to a packageon the PKLIST for the plan.

error-typeType of error: WARNING or ERROR.

auth-idAuthorization ID of the invoker of the BINDsubcommand.

package-nameName of the package in the following format'location.collection.package.(version)'.

System actionPackage not rebound or freed.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_accesscontrolexitroutine.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_accesscontrolexitroutine.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_bindnv.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_bindnv.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/seca/src/tpc/db2z_explictpackprivilege.html

System programmer responseCheck the SYSPACKAGE catalog table for the correct'location.collection.package.version' to use.

DSNT239I PLAN plan-id CONTAINS NODBRMS AND NO PACKAGES

ExplanationA plan with no DBRMs was rebound with theNOPKLIST option specified. This creates an emptyplan. No SQL can be executed. The individual variablefields contain:plan-id

Plan name specified on the REBIND command.

System actionThis is a warning message. The REBIND process willcontinue.

System programmer responseIf an empty plan is not expected, reissue the REBINDcommand with the PKLIST keyword specifying a newlist.

DSNT240I csect-name bind-type ERROR,ASTERISK NOT ALLOWED ONREMOTE bind-type PACKAGE

ExplanationWhen remotely rebinding or freeing a package, anasterisk (*) cannot be specified anywhere in the nameof a package. In other words, it is not possible toremotely rebind or free multiple packages.

System programmer responseRemove the asterisk and rebind, or free a specificpackage.

Related conceptsConsiderations for binding packages at aremote location (Db2 Application programmingand SQL)Related referenceREBIND PACKAGE (DSN) (Db2 Commands)FREE PACKAGE (DSN) (Db2 Commands)

DSNT241I bind-type AUTHORIZATION error-type ON PLAN plan-idAUTHORIZATION ID auth-id NOTAUTHORIZED TO EXECUTEPACKAGE package-name

ExplanationThe indicated authorization ID does not have EXECUTEauthority on the specified package in the package list.If the access control authorization exit is active andthe AUTHEXIT_CHECK subsystem parameter is set toDB2, this error might occur if ACEE cannot be createdfor the indicated authorization ID.bind-type

Type of bind subcommand: BIND or REBINDerror-type

Type of error: WARNING or ERROR. IfVALIDATE(BIND) was specified, this is an ERRORmessage. Otherwise, it is a WARNING message.


auth-idAuthorization ID of the plan owner. Attention: Ifyou are using a trusted context, the token auth-idmight return a role instead of an authorization ID.A role is returned, if a role was in effect and theauthorization checking is performed against therole rather than the authorization ID of the session,when the condition was encountered. The role isreturned in the following format as a single token:ROLE: role-name.

package-nameName of the package (collection.package). Thelocation of the package is the local Db2 locationname.

System actionIf the bind subcommand was invoked withVALIDATE(BIND), the BIND or REBIND operation is notperformed. If VALIDATE(RUN) was used then the BINDor REBIND operation will continue.

System programmer responseThe indicated plan owner should be granted theEXECUTE privilege on the package. If you use theaccess control authorization exit, ensure that theindicated authorization ID is defined in RACF andgranted the indicated privilege in RACF.

DSNT242I bind-type ERROR USING auth-idAUTHORITY NO BIND OR REBINDSUBCOMMANDS ARE ALLOWEDFOR THIS AUTHID

ExplanationThe authorization ID is not allowed to perform theindicated 'bind-type' against a plan or packagebecause entries in the RLST table prohibit binding and


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/apsg/src/tpc/db2z_bindpackageremote.html




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_freepackage.html

rebinding by this authorization ID, or all authorizationIDs.bind-type

Type of bind subcommand: BIND or REBINDauth-id

Authorization ID of the plan or package owner.Attention: If you are using a trusted context, thetoken auth-id might return a role instead of anauthorization ID. A role is returned, if a role was ineffect and the authorization checking is performedagainst the role rather than the authorization ID ofthe session, when the condition was encountered.The role is returned in the following format as asingle token: ROLE: role-name.

System actionThe plan or package is not bound or rebound.

System programmer responseIf the indicated authorization ID should be allowed tobind, change the entry in the active RLST table.

DSNT243I BIND ERROR FOR PACKAGE = pkg-id CONTOKEN = 'contoken'X IS NOTUNIQUE SO IT CANNOT BECREATED

ExplanationAn attempt is made to add or replace a package with aconsistency token that is not unique for that package.In other words, the combination of'location.collection.package.consistency-token'already exists.pkg-id

Fully qualified name of the package.contoken

Consistency token in hexadecimal.

System actionThe BIND will fail.

System programmer responseCheck the SYSIBM.SYSPACKAGE catalog table fornames of existing application packages with theindicated consistency token. Re-issue the BINDsubcommand such that the'location.collection.package.consistency-token' isunique within the catalog. The following SQLstatement can be used to query the catalog,

SELECT COLLID,NAMEFROM loc-id.SYSIBM.SYSPACKAGEWHERE HEX(CONTOKEN) = 'contokn';

DSNT244I bind-type ERROR keywordKEYWORD IS NOT SUPPORTEDFOR REMOTE PROCESSING

CLUSTERED = clusteredCLUSTERRATIO = clusterratioCLUSTERRATIOF = clusterratiofFIRSTKEYCARD = firstkeycardFIRSTKEYCARDF = firstkeycardfNLEAF = nleafNLEVELS = nlevelsSPACEF = spacefDATAREPREATFACTORF = datarepeatfactorf

ExplanationThe indicated keyword is not supported for the remotebind or rebind subcommand.bind-type

Type of bind subcommand: BIND or REBINDkeyword

Name of the keyword that is not supported.

Programmer responseCorrect the syntax and reissue the command.

Related referenceBIND PACKAGE (DSN) (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)REBIND PLAN (DSN) (Db2 Commands)

DSNT245I LOCATION location CANNOT BESPECIFIED. THE LOCAL DB2 ISNOT DEFINED

ExplanationSince the local Db2 location name is undefined, nolocation name may be given when specifying apackage name on a bind subcommand.location

Location specified on the bind subcommand.

\

System actionThe bind subcommand was not performed.






System programmer responseThe location name of the local Db2 must be defined inBSDS if the location is used in the BIND, REBIND, orFREE subcommand.

DSNT246I bind-type FOR PACKAGE package-name WITH MARK release-dependency-mark FAILEDBECAUSE PACKAGE DEPENDS ONFUNCTIONS OF THE RELEASEFROM WHICH FALL BACK HASOCCURRED

ExplanationThe named package depends on a function of Db2which is not supported by the currently active release.bind-type

Type of bind subcommand: REBINDpackage-name

Name of the package in the following format:'location.collection.package.(version)'

release-dependency-markA one-character mark showing the oldest releaseof the Db2 which can support this package. Therelease dependency mark for the package is keptin the IBMREQD column in the Db2 catalog inSYSIBM.SYSPACKAGE.

System actionThe 'bind-type' operation for this package is notperformed.

System programmer responseWarn users not to use plans containing this packageuntil the Db2 subsystem has been remigrated to thenewer release.

User responseThe package cannot be bound until the Db2 subsystemis remigrated to the newer release.

DSNT247I bind-type ERROR object-type NOTFOUND FOR object-type = object-name

ExplanationYou attempted to FREE or REBIND multiple plans orpackages using the asterisk (*) but no plans orpackages were found.bind-type

Type of bind subcommand: REBIND or FREE

object-typeType of object to be freed or rebound: PLAN orPACKAGE

object-nameIf object-type is PLAN, object-name is the name ofthe application plan. Otherwise, it is the name ofthe package in 'location.collection.package'format.

System actionThe REBIND or FREE operation is not performed.

User responseCheck the plan or package name. If it is correct, noplans or packages were found and no operation can beperformed; otherwise, correct the plan or packagename and reissue the REBIND or FREE subcommand.

DSNT249I csect-name bind-type WARNINGFOR PLAN plan-name keywordLOCATION-ID location-id NOTFOUND IN SYSIBM.LOCATION

ExplanationA 'location-id' was specified on the PKLIST orCURRENTSERVER keyword on a bind subcommand.That location is not defined in the SYSIBM.LOCATIONStable.bind-type

Type of bind subcommand: BIND or REBINDplan-name

Name of the plankeyword

The bind subcommand containing the nonexistentlocation: PKLIST or CURRENTSERVER

location-idThe nonexistent location

System actionThe bind process will continue.

System programmer responseDefine the appropriate 'location-ids' in theSYSIBM.LOCATION catalog table prior to executing theplan.

DSNT250I BIND UNABLE TO OPEN DBRMLIBRARY USING authorization-idAUTHORITY object-type = object-name


ExplanationThe BIND subcommand was unable to open the DBRMpartitioned data set(s).authorization-id

Authorization ID of the invoker of the BINDsubcommand.

object-typePLAN | PACKAGE


System programmer responseDetermine why the BIND subcommand was unable toopen the DBRM library, and correct the problem.

User responseContact the system programmer, providing all materialassociated with the error.






.

DSNT251I BIND UNABLE TO LOCATE DBRMLIBRARY MEMBERS USINGauthorization-id AUTHORITYobject-type = object-name

ExplanationThe BIND subcommand received an I/O error whileattempting to locate the specified DBRM librarymember(s).authorization-id

Authorization ID of the invoker of the BINDsubcommand.

object-typePLAN | PACKAGE


System programmer responseCorrect the reason for the I/O error, and reissue theBIND subcommand.






.

DSNT252I csect-name bind-type OPTIONSFOR PLAN plan-name

bind-option option-value

…


ExplanationThis message shows the BIND or REBIND options thatwere used for the plan during bind or rebindprocessing.


bind-typeThe type of operation: BIND or REBIND.

plan-nameThe plan that was processed.

bind-optionThe name of a BIND PLAN or REBIND PLAN option.

option-valueThe value of a BIND PLAN or REBIND PLAN option.



DSNT253I csect-name bind-type OPTIONSFOR PLAN plan-name


…


ExplanationThis message shows the BIND or REBIND options thatwere used for the plan during bind or rebindprocessing.



plan-nameThe plan that was processed.

bind-optionThe name of a BIND PLAN or REBIND PLAN option.

option-valueThe value of a BIND PLAN or REBIND PLAN option.


DSNT254I csect-name bind-type OPTIONSFOR PACKAGE = package-name


…


ExplanationThis message shows the BIND or REBIND options thatwere used for the package during bind or rebindprocessing.



package-nameThe package that was processed.

bind-optionThe name of a BIND PACKAGE or REBINDPACKAGE option.

option-valueThe value of a BIND PACKAGE or REBINDPACKAGE option.



ExplanationThis message shows the BIND or REBIND options thatwere used for the local package during bind or rebindprocessing.




The message heading text is followed by a list ofoption names and settings.




Related referenceBIND PACKAGE (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)

DSNT256I DBRM MEMBER member-name ISEMPTY, A PACKAGE CANNOT BEBOUND

ExplanationThe named DBRM member is empty, a package cannotbe created.

System actionNo package is created.




DSNT257I BIND ERROR, PACKAGE package-name CANNOT BE CREATEDBECAUSE IT HAS THE SAME NAMEAS THE PACKAGE BEING COPIED

ExplanationThe location and collection-id of the package beingcreated are the same as the local location and thecollection-id specified with the COPY keyword. Youcannot create a package that is the same name as thepackage being copied.package-name

Name of the package (location.collection.package.(version))

System actionThe package is not bound.

System programmer responseChoose a different collection id for the package you arecreating and resubmit the subcommand.

DSNT258I bind-type WARNING FOR PLANplan-name THE LOCATION-IDlocation-id SPECIFIED INCURRENTSERVER MAY NEED APACKAGE LIST

ExplanationIf binding a PLAN with a nonlocal location specified inthe CURRENTSERVER, a package list is required usingthe PKLIST keyword to access any packages at thelocation specified.bind-type


Name of planlocation-id

Location of CURRENTSERVER


System programmer responseAdd a package list with package(s) that reference thelocation specified in the CURRENTSERVER or deletethe CURRENTSERVER from the BIND or REBINDsubcommand.

DSNT259I bind-type WARNING FOR PLANplan-name NO PACKAGES IN THE

PACKAGE LIST REFERENCE THELOCATION-ID location-idSPECIFIED IN CURRENTSERVER

ExplanationThere are no packages in the package list thatreference the location specified in theCURRENTSERVER keyword.bind-type


Name of planlocation-id

Location of CURRENTSERVER


System programmer responseChange 'location-ids' for the packages in the packagelist to reference the location in the CURRENTSERVERor change the location specified in CURRENTSERVER.

DSNT260I csect-name bind-type - THESUBMITTED PARAMETERS RESULTIN AN INVALID COMBINATION OFbind-option1 AND bind-option2FOR object-type = object-name

ExplanationThe BIND or REBIND subcommand has beensubmitted with an invalid combination of bind optionor parameter values.bind-type

Type of bind subcommand: BIND or REBIND.object-type

PLAN or PACKAGEobject_name

If object-type is PLAN, object-name is the name ofthe application plan.

If object_type is PACKAGE, object_name is thename of the package in the format location-id.collection-id.package-id.

bind-option1 and bind-option2The invalid combination of bind option values,where bind-option1 and bind-option2 are each anoption name and value.

If object-type is PLAN, then one of the followingapplies:


• bind-option1 was used on the REBINDsubcommand and bind-option2 exists in theSYSIBM.SYSPLAN catalog table for PLAN object-name, or

• bind-option2 was used on the REBINDsubcommand and bind-option1 exists in theSYSIBM.SYSPLAN catalog table for PLAN object-name.

If object-type is PACKAGE, then one of thefollowing applies:

• bind-option1 was used on the BIND COPY orREBIND subcommand and bind-option2 exists inthe SYSIBM.SYSPACKAGE catalog table forPACKAGE object-name, or

• bind-option2 was used on the BIND COPY orREBIND subcommand and bind-option1 exists inthe SYSIBM.SYSPACKAGE catalog table forPACKAGE object-name.

The combination of bind-option1 and bind-option2 isnot supported by Db2.

System actionThe BIND or REBIND process is terminated for theindicated plan or package.

User responseRemove the invalid combination of bind options andreissue the BIND or REBIND command.

Related referenceBIND PACKAGE (DSN) (Db2 Commands)BIND and REBIND options for packages, plans,and services (Db2 Commands)BIND PLAN (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)REBIND PLAN (DSN) (Db2 Commands)SYSPACKAGE catalog table (Db2 SQL)SYSPLAN catalog table (Db2 SQL)

DSNT261I bind-type WARNING FOR object-type = object-name ALLCONNECTION TYPES AREDISABLED

ExplanationAll possible connection types are disabled. The plan orpackage cannot be executed.bind-type

Type of bind subcommand: BIND or REBINDobject-type

PLAN or PACKAGE



System programmer responseDelete one or more connection types from DISABLEclause or add a list of connection names associatedwith one of the connection types (DLIBATCH, CICS,IMSBMP, IMSMPP, or REMOTE. REMOTE is only validfor BIND/REBIND PACKAGE)

DSNT262I csect-name bind-type WARNING -ISOLATION old-iso NOTSUPPORTED. CHANGING TOISOLATION new-iso

ExplanationDb2 does not support the isolation level specified onthe local BIND or REBIND PACKAGE subcommand.The isolation level specified by new-iso is usedinstead.

System actionProcessing continues

User responseIf the new isolation level is not satisfactory, change theISOLATION option on the BIND or REBIND PACKAGEsubcommand and rebind the package. Use a value thatDb2 supports.

Severity4

DSNT263I csect-name bind-type FOR object-type = object-name FAILEDBECAUSE THE bind-type DEPENDSON FUNCTIONS IN A LATER DB2RELEASE WITH MARK release-dependency-mark OR HIGHER

ExplanationThe current Db2 does not support a bind option orfeature specified in the indicated bind subcommand.The bind option or feature depends on functions in alater Db2 release.








https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsyspackagetable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsysplantable.html




If object-type is PACKAGE, object-name is thename of the package in the format location-id.collection-id.package-id.

release-dependency-markA one-character mark indicating the oldest Db2release that can support the bind subcommand.

This message can be issued in one of the followingsituations:

• When the DSN command explicitly or implicitly usesthe name of a Db2 subsystem that does not supporta bind option or feature used in the DSN bindsubcommand bind-type.

• When the DSN command uses a group attachmentname for a Db2 data sharing group and the receivingDb2 data sharing member does not support a bindoption or feature used in the DSN bind subcommandbind-type.

• When attempting to use new function before newfunction mode has been enabled.

System actionThe bind-type operation is not performed.

System programmer responseSee the 'User Response' section of this message.

User responseIn the DSN command, specify the name of a Db2subsystem having release dependency mark release-dependency-mark or higher that supports all of thebind options or features used in the bind-typesubcommand.

The IBMREQD columns in the SYSIBM.SYSPLAN orSYSIBM.SYSPACKAGE catalog tables contains therelease dependency marks.

Related referenceDb2 catalog tables (Db2 SQL)SYSPLAN catalog table (Db2 SQL)SYSPACKAGE catalog table (Db2 SQL)

DSNT264I csect-name bind-type bind-subtypeERROR USING auth-id AUTHORITY

PACKAGE package-name IS Apackage-type PACKAGE

ExplanationIf this error is issued for TRIGGER package, then:

• A DSN subcommand other than REBIND TRIGGERPACKAGE was issued to rebind a trigger package. Torebind a trigger package, use the DSN subcommandREBIND TRIGGER PACKAGE.

• A statement other than DROP TRIGGER was issuedto free a trigger package. To free a trigger package,use the SQL statement DROP TRIGGER.

• A DSN BIND subcommand was issued with the COPYoption for a trigger. You cannot copy a triggerpackage for a trigger.

If the error is issued for native SQL procedure package:

• A statement other than the SQL statement DROPPROCEDURE was issued to free a package for anative SQL procedure. To free a native SQLprocedure package, you must use the SQL statementDROP PROCEDURE.

If the error is issued for REST SERVICE package, then:

• To replace a REST SERVICE package, you must usethe FREE SERVICE and BIND SERVICE commands.

If the error is issued for NON-REST SERVICE package,then:

• A non-REST service package was the object of theFREE SERVICE command. FREE SERVICE can only beused to free a REST SERVICE package.

The message tokens are:


bind-subtypeSubtype of bind subcommand: REPLACE,TRIGGER, or DEPLOY

auth-idAuthorization ID of the user that attempted theprohibited action

package-nameName of the package, in the following format:

collection.package

package-typeType of package: TRIGGER, NATIVE SQLPROCEDURE, REST SERVICE.


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_catalogtablesintro.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsysplantable.html


System actionThe package is not copied, rebound, freed, orreplaced.

System programmer responseCheck the SYSIBM.SYSPACKAGE catalog table fornames of existing trigger packages or native SQLprocedure packages. Do not issue the specified bindsubcommand for a trigger package or a native SQLprocedure package.

DSNT265I csect-name bind-type bind-subtypeERROR USING auth-id AUTHORITYPACKAGE package-name IS NOT Apackage-type PACKAGE

ExplanationThe subcommand REBIND TRIGGER PACKAGE can beused only for trigger packages. The subcommandBIND PACKAGE DEPLOY can be used only for nativeSQL PL procedure packages. The subcommand FREEPACKAGE can be used only for non-trigger and non-native SQL PL procedure packages.

The message tokens are as follows:bind-type

Type of bind subcommand: REBIND, FREEbind-subtype

Subtype of bind subcommand: TRIGGER, DEPLOYauth-id

Authorization ID attempting the prohibited actionpackage-name

Name of the package in the following format:

'collection.package'

package-typeType of package: TRIGGER, NATIVE SQL PLPROCEDURE

System actionThe package specified is not rebound, deployed, orfreed.

System programmer responseFor a package that is not a trigger package, rebindusing the subcommand REBIND PACKAGE. Re-invokethe bind subcommand with a 'collection.package' thatis an accepted package.

DSNT266I csect-name bind-type FOR object-type = object-name FAILED. THETOTAL LENGTH OF THE PATH

SCHEMA NAME LIST EXCEEDS 254CHARACTERS WITH SCHEMANAME schema-name

ExplanationDb2 uses the schema name list you specified in thebind option PATH to set the Db2 SQL Path that will beused for the bind process. The SQL Path is aVARCHAR(254) string containing the list of schemanames you specified, where each schema name isdelimited with double quotes and separated from thenext schema name by a comma. The total length ofthis SQL Path string, including the delimiters andcommas, cannot exceed 254 characters. The indicatedschema name schema-name in the bind option PATHcauses the SQL Path string to exceed 254 characters.bind-type


PLAN or PACKAGEobject-name

If object-type is PLAN, object-name is the name ofthe plan.

If object-type is PACKAGE, object-name is thename of the package in the format 'location-id.collection-id.package-id.(version-id)'.

schema-nameThe schema name specified in the bind optionPATH causing the SQL Path to exceed 254characters.

System actionThe bind-type operation is not performed.

System programmer responseSee the 'User Response' section of this message.

User responseIn the bind option PATH, specify a schema name listthat does not cause the SQL Path to exceed 254characters.

For more information about the bind option PATH andthe schema name list, please see: CommandReference.

DSNT267I csect-name bind-type FOR object-type = object-name FAILED. FORbind-type OPTION option-name,THE VALUE CONTAINING string ISINVALID BECAUSE OF A SYNTAXERROR OR INVALID CHARACTERS.


ExplanationA BIND/REBIND command failed because a Db2parser error SQLCODE was received when Db2attempted to parse the bind option value.bind-type


PLAN or PACKAGEoption-name

Name of the bind option.string

The string that has a syntax error or invalidcharacters.

System actionThe package is not bound or rebound.

User responseCheck the string that is invalid. Modify it and try thecommand again.

DSNT268I csect-name bind-type FOR object-type = object-name FAILED. FORbind-type OPTION option-name,THE VALUE OR NAME string IS TOOLONG. THE MAXIMUM ALLOWABLELENGTH FOR THE VALUE OR NAMEIS max-size.

ExplanationA BIND/REBIND command failed because Db2 parserSQLCODE -107 was received when Db2 attempted toparse the bind option value.bind-type


PLAN or PACKAGEoption-name

Name of the bind option.string

The string that has a syntax error or invalidcharacters.

max-sizeThe maximum length allowed.

System actionThe package is not bound or rebound

User responseCheck the string that is too long. Modify it and try thecommand again.

DSNT269I csect-name Db2 SWITCHED TOTHE copy-indicator COPY OFPACKAGE package-name. THISCOPY IS NOT EXECUTABLEWITHOUT AN EXPLICIT REBINDOR AUTOBIND (REASON=reason-code).

ExplanationThe command was successfully processed, but theinvalid copy has replaced the current package copy.This copy cannot be used.csect-name


copy-indicatorIndicates whether the invalid copy that was usedwas the previous or original package copy.Expected values are PREVIOUS or ORIGINAL.

package-nameThe invalid package, in the format location-id.collection-id.package-id.(version-id).

reason-codeA numeric value that indicates why the copy is notexecutable.01

The copy is invalid.02

The copy is from a prior release that is nolonger executable without an explicit REBINDor autobind.

System actionThe command was successfully processed, but theinvalid copy has replaced the current package copy,which cannot be used.

User responseDetermine why the package is invalid and resolve thatcondition before invoking the package. Otherwise, thepackage will be automatically rebound at the firstinvocation.

Severity4 (warning)


Related conceptsAutomatic rebinds (Db2 Applicationprogramming and SQL)Changes that invalidate packages (Db2Application programming and SQL)Related referenceSYSPACKAGE catalog table (Db2 SQL)REBIND PACKAGE (DSN) (Db2 Commands)

DSNT270I THE FOLLOWING SQLCAINFORMATION WAS RETURNEDFROM subsystem-id

• SQLCODE = sql-code• SQLSTATE = sql-state• SQLERRMT = sqlca-tokens• SQLWARN warn_fields

ExplanationA warning or error has been received from a databaseserver using Distributed Relational DatabaseArchitecture™ (DRDA) during remote program BINDprocessing.subsystem-id

The database server.sql-code

A numeric value that indicates why the SQLstatement execution was unsuccessful.

sql-stateThe corresponding SQLSTATE for the SQLCODE.

sqlca-tokensTokens that are passed in the message portion ofthe SQLCA for problem determination.

warn_fieldsThe warning information indicators.

System actionSee the System Action associated with the indicatedSQLCODE.

System programmer responseSee the Programmer Response associated with theindicated SQLCODE and/or SQLSTATE. Take note of thewarning or error (as indicated in the SQLCODE,SQLSTATE, or one or more of the SQLWARN fields), anddetermine if a program change is necessary. A changeto the application might be necessary or the systemprogrammer might have to be consulted depending onthe situation.

If you suspect an error in Db2, you might need toreport the problem. For information about identifying






Related conceptsSQL communication area (SQLCA) (Db2 SQL)Related referenceDescription of SQLCA fields (Db2 SQL)

DSNT271I THE FOLLOWING SQLCAINFORMATION WAS RETURNEDFROM subsystem-id

• SQLCODE = sql-code• SQLSTATE = sql-state• SQLERRMT = sqlca-tokens• SQLWARN warn_fields• STATEMENT = statement_number

ExplanationA warning or error has been received from a databaseserver using Distributed Relational DatabaseArchitecture (DRDA) during remote program BINDprocessing.subsystem-id

The database server.sql-code

A numeric value that indicates why the SQLstatement execution was unsuccessful.

sql-stateThe corresponding SQLSTATE for the SQLCODE.

sqlca-tokensTokens that are passed in the message portion ofthe SQLCA for problem determination.

warn_fieldsThe warning information indicators.

statement_numberThe statement number of the failing statement.

System actionSee the System Action associated with the indicatedSQLCODE.











https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_descriptionofsqlcafields.html

System programmer responseTake note of the warning or error (as indicated in theSQLCODE, SQLSTATE, or one or more of the SQLWARNfields), and determine if a program change isnecessary. Depending on the situation, a change to theapplication might be necessary or the systemprogrammer might have to be consulted.






Related conceptsSQL communication area (SQLCA) (Db2 SQL)Related referenceDescription of SQLCA fields (Db2 SQL)

DSNT274I ERROR USINGSQLDDNAME(ddname): error-text

ExplanationDb2 could not open or read the data set or fileassigned to the ddname DD statement in the JCL forthe BIND SERVICE subcommand because one or moreof the conditions specified in error-text occurred.

.ddname

Name of a data set or file that is specified for theSQLDDNAME parameter of the BIND SERVICEsubcommand.

error-textDescription of any of the following conditions thatcan cause the error:DDNAME CANNOT BE OPENED

The DD job card is not provided in the JCL or anerror prevents the opening of the data set orfile. Review all job messages.

INVALID DSORG OR RECFM SPECIFICATIONThe data set, the fully-qualified member of aPDS/PDSE library, or the zFS or UNIX file hasinvalid characteristics. The organization of the

data set or file must be sequential. The formatmust be F (fixed-length records, unblocked),FB (fixed-length records, blocked), V (variable-length records, unblocked), or VB (variable-length records, blocked). Make sure thatRECFM=VB is specified with the DD statementwhen it refers to a zFS or UNIX file.

EMPTY DATASET OR FILEThe end of file is reached before any data isread in.

I/O ERROR DETECTED - error-descWhen the ddname data set or file is read, anI/O error with error-desc is detected. Onepossible cause for the I/O error"WRNG.LEN.RECORD" is that a member nameis not specified along with the PDS or PDSElibrary name for the ddname DD statement.See "SYNADAF Error Descriptions" in the z/OSdocumentation for more information.

System actionThe BIND SERVICE subcommand operation is notperformed.

System programmer responseIf an I/O error is detected, verify that the data set orfile specified for the DD statement is a supportedDSORG or RECFM and that the data set or file existsand can be opened.

User responseVerify that the BIND SERVICE job JCL contains a validddname DD specification. Make sure that the data setor file actually exists, contains a valid SQL statement,and can be opened and read.

Severity8 (error)

Related referenceBIND SERVICE (DSN) (Db2 Commands)FREE SERVICE (DSN) (Db2 Commands)


ExplanationThis message shows the BIND or REBIND options thatwere used for the local package during bind or rebindprocessing.





https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_descriptionofsqlcafields.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_bindservice.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/comref/src/tpc/db2z_cmd_freeservice.html




The message heading text is followed by a list ofoption names and settings.




Related referenceBIND PACKAGE (DSN) (Db2 Commands)REBIND PACKAGE (DSN) (Db2 Commands)

DSNT276I SUCCESSFUL bind-type FORSERVICE = service-name

ExplanationA BIND SERVICE or FREE SERVICE subcommand hascompleted successfully.bind-type

Type of bind subcommand: BIND or FREEservice-name

Name of the service in the format of'location.collection.service.(version)'

System actionThe service is successfully bound or freed.


DSNT277I UNSUCCESSFUL bind-type FORSERVICE = service-name

ExplanationThe BIND SERVICE or FREE SERVICE command failedbecause of errors during the command processing.

bind-typeType of bind subcommand: BIND or FREE

service-nameName of the service in the format of'location.collection.service.(version)'

System actionThe service-name service was not bound or freed.

System programmer responseSee the preceding error message or messages todetermine the cause and respond accordingly.


DSNT278I bind-type SERVICE ERROR FORservice-name BECAUSE error-text

ExplanationThe BIND SERVICE or FREE SERVICE command failedbecause one or more of the conditions specified inerror-text occurred.


service-nameName of the package in the format of'location.collection.service.(version)'.

error-textDescription of any of the following conditions thatcan cause the error:

• SERVICE DOES NOT EXIST.• SERVICE ALREADY EXISTS.• THE SQL STATEMENT IS NOT SUPPORTED.• CALL HOST-VARIABLE IS NOT SUPPORTED. USE

CALL PROCEDURE-NAME INSTEAD.• OFFLOAD OF NON-SELECT STATEMENTS IS NOT

SUPPORTED.• STATEMENT CONTAINS UNBALANCED

DELIMITERS.• STATEMENT CONTAINS BOTH HOSTVARS AND

PARAMETER MARKERS.• STATEMENT CONTAINS A ZERO LENGTH

HOSTVAR.• STATEMENT CONTAINS NO HOSTVAR

IDENTIFIER AFTER COLON.








System actionThe service-name service is not bound or freed.

System programmer responseSee error-text to determine the cause of the error andrespond accordingly.


DSNT279I csect-name A REST SERVICECANNOT BE bind-result-typeUSING THE bind-type PACKAGECOMMAND

ExplanationA BIND PACKAGE COPY or a FREE PACKAGEsubcommand was issued to bind or free a RESTservice. A Db2 REST service can be only bound orfreed by using the BIND SERVICE or FREE SERVICEsubcommand.

bind-result-typeResult type of bind subcommand: BOUND orFREED


service-nameName of the service in the format of'location.collection.service.(version)'

System actionThe TSO Attachment Facility is ready for more input.

User responseUse the BIND SERVICE or FREE SERVICEsubcommand to bind or free a REST service.


DSNT280I bind-command QUERY FOR query-type = query-identifierSUCCESSFUL

ExplanationA BIND operation has completed successfully.

bind-commandThe type of command that resulted in themessage:BIND

For BIND QUERY commands.FREE

For FREE QUERY commands.LOOKUP

For BIND QUERY commands when theLOOKUP(YES) option is in effect.

query-typeInformation that identifies the query:QUERYNO

The query is identified by the query number(QUERYNO) in the tableDSN_USERQUERY_TABLE.

QUERYIDThe query is identified by the query ID(QUERYID) in the table SYSIBM.SYSQUERY.

query-identifierThe query number or query ID, depending on thequery-type value.

When bind-command is LOOKUP, an instance of theDSNT280I message is issued for each row in theDSN_USERQUERY_TABLE that does not have matchingrows in both the SYSIBM.SYSQUERY andSYSIBM.SYSQUERYPLAN catalog tables.



Related tasksSpecifying optimization parameters at thestatement level (Db2 Performance)Related referenceBIND QUERY (DSN) (Db2 Commands)DSN_USERQUERY_TABLE (Db2 Performance)SYSQUERY catalog table (Db2 SQL)Related informationDSNT281Ibind-command QUERY FOR query-type = query-identifier NOT SUCCESSFUL. REASON: reason-textDSNT290Ibind-command QUERY COMMAND COMPLETEDDSNT291I






https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_createzparmhint.html



https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/usrtab/src/tpc/db2z_dsnuserquerytable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsysquerytable.html

bind-command QUERY COMMAND NOTSUCCESSFUL. REASON: reason-text

DSNT281I bind-command QUERY FOR query-type = query-identifier NOTSUCCESSFUL. REASON: reason-text

ExplanationErrors were detected during processing of a BINDQUERY or related operation on a query.

bind-commandThe type of command that resulted in themessage:BIND

For BIND QUERY commands.FREE

For FREE QUERY commands.LOOKUP

For BIND QUERY commands when theLOOKUP(YES) option is in effect.

query-typeInformation that identifies the query:QUERYNO

The query is identified by the query number(QUERYNO) in the tableDSN_USERQUERY_TABLE.

QUERYIDThe query is identified by the query ID(QUERYID) in the table SYSIBM.SYSQUERY.

query-identifierThe query number or query ID, depending on thequery-type value.

reason-textreason-text is one of the following values:1. PACKAGE INFORMATION IS INVALID

The specified package information is not valid2. THE HINT, OPTION, OR OVERRIDE WASNOT FOUND

The LOOKUP option was specified and thespecified hint, option, or override was notfound in the catalog tables.

3. THE STATEMENT TEXT CONTAINS ANERROR

The statement text contains an error.4. THE STATEMENT TYPE IS NOT SUPPORTED

The statement is of a type that is not supportedby the BIND QUERY command.

5. BIND QUERY DOES NOT SUPPORTpackage-type PACKAGES

The query is from a package of a type that isnot supported by the BIND QUERY command.Example values for package-type mightinclude:

• 'TRIGGER'• 'PROCEDURE'• 'FUNCTION'

6. THE qualified-table-column COLUMNCONTAINS AN INVALID VALUE = invalid-value

The input table column that is identified byqualified-table-column contains an invalidvalue, which is provided as invalid-value.

7. A REQUIRED object-typequalifier.object-name DOES NOT EXIST

The specified object does not exist.8. THE qualified-table-column COLUMNFOR PREDNO predno-value CONTAINS ANINVALID VALUE = invalid-value

The input table column that is identified byqualified-table-column contains an invalidvalue, which is provided as invalid-value.predno-value identifies the PREDNO value ofthe row that contains the invalid value.

9. THE qualified-table-column COLUMNCONTAINS AN INVALID COMBINATION OFVALUES: invalid-combination

qualified-table-column identifies a column thatcontains an invalid combination of values inseveral rows. Example values for invalid-combination include:NON-MATCHING WEIGHT VALUES FOR ROWSWITH THE SAME INSTANCE VALUE:instance-value

For each query, every row with the sameinstance value must of have the sameweight value.

SUM OF INSTANCE WEIGHTS > 1.0For each query, the sum of weights for allinstance values must be less-than or equalto 1.0.

NUMBER OF DISTINCT INSTANCE VALUESinstance-count IS GREATER THAN max-instances.

Too many instances where specified. Db2supports only as many instances as thevalue specified by max-instances

10. THE qualified-table-column COLUMNCONTAINS AN INVALID COMBINATION OF


VALUES FOR PREDNO = predno-value:invalid-combination

The input table column that is identified thequalified-table-column value contains aninvalid combination of values in several rows.Example invalid-combination values mightinclude:

• MULTIPLE ROWS CONTAIN THE SAMEINSTANCE VALUE instance-value

• DUPLICATE ROWS EXIST FOR THE SAMECOMPOUND PREDICATE

The predno-value identifies the PREDNO valueof the rows that contain the invalidcombination of values.

11. INPUT TABLE COLUMNS CONTAININCOMPATIBLE VALUES additional-information

The value of additional-information is a stringthat identifies the reason that the commandfailed. Examples might include:

• THE VALUE OF THE STARJOIN COLUMNCANNOT BE 'Y' WHEN MORE THAN ONESELECTIVITY INSTANCE EXISTS

• A VALUE IN THE PREDNO COLUMN OFDSN_SELECTIVITY TABLE DOES NOT EXISTIN DSN_PREDICATE_TABLE

• NONE OF THE FOLLOWING VALUESCONTAINS A 'Y' VALUE: ACCESSPATH_HINT,SELECTIVITY_OVERRIDE, ANDOPTION_OVERRIDE

• ONE OF THE FOLLOWING COLUMNSCONTAINS A BLANK VALUE:ACCESSPATH_HINT,SELECTIVITY_OVERRIDE, ANDOPTION_OVERRIDE. ALL MUST CONTAINVALUES WHEN ANY IS SPECIFIED

When bind-command is LOOKUP, an instance of theDSNT281I message is issued for each row in theDSN_USERQUERY_TABLE that has matching rows inboth the SYSIBM.SYSQUERY andSYSIBM.SYSQUERYPLAN catalog tables.

System actionThe query is not processed.

System programmer responseUse the information provided in this code and othermessages issued in conjunction with this one todetermine the reason why the query could not beprocessed.

Related tasksSpecifying optimization parameters at thestatement level (Db2 Performance)Overriding predicate selectivities at thestatement level (Db2 Performance)Related referenceBIND QUERY (DSN) (Db2 Commands)DSN_USERQUERY_TABLE (Db2 Performance)SYSQUERY catalog table (Db2 SQL)SYSQUERYPLAN catalog table (Db2 SQL)SYSQUERYOPTS catalog table (Db2 SQL)SYSQUERYSEL catalog table (Db2 SQL)SYSQUERYPREDICATE catalog table (Db2 SQL)Related informationDSNT280Ibind-command QUERY FOR query-type = query-identifier SUCCESSFULDSNT290Ibind-command QUERY COMMAND COMPLETEDDSNT291Ibind-command QUERY COMMAND NOTSUCCESSFUL. REASON: reason-text

DSNT282I bind-command QUERYAUTHORIZATION ERROR USINGauthorization-id AUTHORITY

ExplanationA BIND operation was invoked by an authorization IDthat does not have the required authorization.

bind-commandThe BIND operation: BIND, REBIND, or FREE.

authorization-idThe authorization ID of the invoker of thecommand.

System actionThe operation is not performed.

User responseResubmit the command from an authorization ID thathas the required authorization.

DSNT284I THE command-name COMMANDONLY PROCESSES DYNAMIC SQLQUERIES. ANY HINTS (SOURCE =0) WERE NOT PROCESSED.

ExplanationAn attempt was made to rebind or free a static SQLstatement or a hint.




https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_createselecthint.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/perf/src/tpc/db2z_createselecthint.html


https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/usrtab/src/tpc/db2z_dsnuserquerytable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsysquerytable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsysqueryplantable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsysqueryoptstable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsysqueryseltable.html

https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/cattab/src/tpc/db2z_sysibmsysquerypredicatetable.html

Documents

Db2 11 for z/OS: Messages - IBM · 2021. 1. 13. · About this information. This information helps you to understand the messages that you could receive while working with Db2 11