Professional Documents
Culture Documents
SC18-9162-02
IBM DB2 Information Integrator
SC18-9162-02
Before using this information and the product it supports, be sure to read the general information under “Notices” on page 185.
This document contains proprietary information of IBM. It is provided under a license agreement and copyright law
protects it. The information contained in this publication does not include any product warranties, and any
statements provided in this manual should not be interpreted as such.
You can order IBM publications online or through your local IBM representative:
v To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/order
v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at
www.ibm.com/planetwide
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 2003, 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
© CrossAccess Corporation 1993, 2003.
Contents
Chapter 1. Console messages Chapter 16. ODBC/CLI error messages
(CAC00001–CAC00808) . . . . . . . . 1 (x00560001–x00560092) . . . . . . . 47
Chapter 5. API-F error messages Chapter 20. Sequential file access error
00120000–0012FFFF (1179648–1245183) 13 messages (0x00590021–0x00590029) . . 79
Chapter 10. Correlation service error Chapter 25. Virtual message interface
messages (00430000–0043FFFF). . . . 23 error messages (00660001–0066000B) . 93
Chapter 11. Change-capture agent error Chapter 26. Local queue layer error
messages (00440000–0044FFFF). . . . 37 messages (00670001–00670014) . . . . 95
Chapter 12. Query processor finite Chapter 27. Socket layer error
state machine error messages messages (00680001–00680033) . . . . 97
(00490001–00490009) . . . . . . . . 39
Chapter 28. Virtual communications
Chapter 13. User exit predefined error interface error messages
messages (004D0000–004DFFFF) . . . 41 (00690001–0069000F) . . . . . . . . 99
iv DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 1. Console messages (CAC00001–CAC00808)
This section contains the console messages (WTOs), which are in the range
CAC00001–CAC00808.
Explanation: The IMS™ BMP/DBB service was being Explanation: The IMS DRA service was being used to
used to access IMS data. The IMS region controller access IMS data. Upon service initialization an error
was reported by the control exit that is used to monitor
Explanation: An operator command was issued to Explanation: Internal error, contact IBM Technical
activate the Logger task. The Logger is active and the Support at www.ibm.com/support.
Controller has established a session with the Logger.
Any errors detected by the Controller will now be CAC00120I RESOURCE MANAGER HAS
logged. RECEIVED CONTROL.
Explanation: The enterprise server resource manager
CAC00114W CONTROLLER: LOGGING that monitors data servers has received control. A data
UNAVAILABLE. server being managed by the enterprise server is
Explanation: An operator command was used to terminating. This is an informational message.
activate the Logger task. The Logger is active but the
Controller was unable to establish a session with the
Logger. The Controller cannot report errors. The data or
enterprise server operational environment is probably
2 DB2 II System Messages for Classic Federation and Classic Event Publishing
configuration. If you cannot determine the cause of the
CAC00121W BAD RETURN CODE FROM WTO.
error, or are running the supplied DB2 Thread
Explanation: The data or enterprise server attempted Management Exit, contact IBM Technical Support at
to issue a WTO message, however, an unexpected www.ibm.com/support.
return code was received from the WTO macro.
CAC00133E DB2 CAF CONNECT SSN=xxxxxxxx,
CAC00122E UNABLE TO ACQUIRE STORAGE. RC=nn, RSN=‘xnnnnnnnnnx’.
Explanation: The data or enterprise server attempted Explanation: The CAF server attempted to connect to
to issue a WTO message, however the data or a DB2 Universal Database (UDB) subsystem and the
enterprise server was unable to allocate storage for the connection failed. The DB2 UDB subsystem is identified
message. Stop the data or enterprise server and by SSN, the failure return code is identified in decimal
increase the REGION size and/or decrease the by RC and the hex reason code is identified by RSN.
MESSAGE POOL SIZE. WTO message storage is See the IBM DB2 Universal Database for OS/390 and z/OS
allocated out of virtual memory that is not controlled Application Programming and SQL Guide for an
by the MESSAGE POOL SIZE setting. explanation of the RC and RSN code displayed. If you
cannot resolve the problem, contact IBM Technical
Support at www.ibm.com/support.
CAC00123W WTO MSG EXCEEDS MAX LENGTH.
Explanation: The data or enterprise server attempted
CAC00134E DB2 CAF OPEN SSN=’xxxxxxxx’,
to issue a WTO message, however, the length of the
PLAN= ’xxxxxxxx’, RC=nn, RSN=
message exceeded 127 characters. The message was not
’xnnnnnnnnx’.
displayed.
Explanation: The CAF server attempted to issue an
open to a DB2 Universal Database (UDB) plan and the
CAC00130E DB2 THREAD MANAGEMENT EXIT -
open failed. The DB2 UDB subsystem is identified by
INIT FAILED RC=nn.
SSN. The plan that was being opened is identified by
Explanation: The DB2® Thread Management Exit PLAN. The failure return code is identified in decimal
issued a nonzero return code when called to perform by RC and in hexadecimal by RSN. See IBM DB2
initialization processing by the CAF service. The RC Universal Database for OS/390 and z/OS Application
identifies the decimal return code returned by the DB2 Programming and SQL Guide for an explanation of the
Thread Management Exit. The CAF service is not RC and RSN code displayed. If you cannot resolve the
operational. See the DB2 Thread Management Exit as problem, contact IBM Technical Support at
named on the SERVICE INFO ENTRY for the DB2 CAF www.ibm.com/support.
service in the master configuration. If you cannot
determine the cause of the error, or are running the
CAC00200I Operator Command.
supplied DB2 Thread Management Exit, contact IBM
Technical Support at www.ibm.com/support. Explanation: An operator command was issued using
the MTO (Master Terminal Operator) interface. The text
of the command is displayed after the message number.
CAC00131E DB2 SUBSYSTEM TERMINATING
This is an informational message. A subsequent WTO
ECB=xnnnnnnnn.
message will indicate whether the command was
Explanation: A console operator requested a processed or not.
shutdown of the DB2 Universal Database™ (UDB)
subsystem with the -STOP DB2 command. The CAF
CAC00201I Operator Command.
thread automatically disconnects from DB2 UDB so that
DB2 UDB can shutdown normally. DB2 UDB access is Explanation: An operator command was issued using
disabled until both the DB2 UDB subsystem and the a remote operator interface. The text of the command is
CAF services defined for the specific subsystem are displayed after the message number. This in an
restarted. informational message. A subsequent WTO message
will not be displayed indicating whether the command
was processed successfully or not.
CAC00132E DB2 THREAD MANAGEMENT EXIT -
TERM FAILED RC=nn.
CAC00202W UNKNOWN COMMAND.
Explanation: The DB2 Thread Management Exit
issued a nonzero code when called to perform Explanation: An invalid or unknown operator
termination processing by the CAF service. The RC command was issued by an MTO or remote operator.
identifies the decimal return code returned by the DB2 See the IBM DB2 Information Integrator Administration
Thread Management Exit. See the DB2 Thread Guide and Reference for Classic Federation and Classic
Management Exit as named on the SERVICE INFO Event Publishing for descriptions of the commands
ENTRY for the DB2 CAF service in the master supported and their syntax.
4 DB2 II System Messages for Classic Federation and Classic Event Publishing
CAC00218W (nn) xxxxxxx CAN ONLY BE AN CAC00224W ORDINAL VALUE nn NOT FOUND.
INTEGER VALUE.
Explanation: This message is in response to a SET
Explanation: This message is in response to a SET operator command. The SET command was attempting
operator command. The configuration parameter you to update a SERVICE INFO ENTRY configuration
are attempting to update only accepts an integer value. parameter. Too many parameters were supplied. See
You have supplied a nonnumeric value. See the IBM the IBM DB2 Information Integrator Administration Guide
DB2 Information Integrator Administration Guide and and Reference for Classic Federation and Classic Event
Reference for Classic Federation and Classic Event Publishing for a description of the syntax of the
Publishing for a description of the syntax of the SERVICE INFO ENTRY configuration parameter.
configuration parameter you are attempting to update.
CAC00225I TOTAL MEMORY nnnK, USED nnnK
CAC00219W SYNTAX ERROR - VALUES NOT (nn%), MAX USED nnnK (nn%).
CONSISTENT FOR xxxxxxxx.
Explanation: This message is in response to a
Explanation: This message is in response to a SET DISPLAY,MEMORY operator command. The TOTAL
operator command. You supplied an invalid value for MEMORY value identifies how much memory (in K)
the configuration parameter you are attempting to was initially allocated for the memory pool. This value
update. See the IBM DB2 Information Integrator represents the amount of memory that was obtained
Administration Guide and Reference for Classic Federation based on the MEMORY POOL SIZE configuration
and Classic Event Publishing for a description of the parameter. The amount of memory allocated is usually
syntax of the configuration parameter you are less than the amount that was requested. The USED
attempting to update. value identifies how much memory (in K) is currently
in use. The next value is the percentage of memory that
is currently used. The MAX USED value identifies the
CAC00220I The xxxxxxxx REMOVED FROM
maximum amount of memory (in K) that has been used
CONFIGURATION.
since the server started. The final value is the
Explanation: This message is in response to a SET percentage of memory that the maximum used
operator command. The requested configuration represents.
parameter has been removed.
CAC00403E ERROR PROCESSING DATA SERVER
CAC00221I (nn) xxxxxxxx RESET TO ITS DEFAULT STARTUP MEMBER nnnnnnn.t.
VALUE.
Explanation: An error has occurred locating or
Explanation: This message is in response to a SET processing the data server start-up member represented
operator command. The requested configuration by nnnnnnn.t. Check to determine whether the server
parameter has been reset to its default value. start-up member is in a library contained in the server
start-up JCL LIBDEF chain.
CAC00222W ENTRY IS ALREADY NULL.
CAC00406E OPEN ERROR, UNKNOWN ACCESS
Explanation: This message is in response to a SET MODE.
operator command. The SET command requested
setting a configuration parameter to its null (default) Explanation: An internal Sequential I/O error has
value, however, the requested configuration parameter been detected. Contact IBM Technical Support at
value is already null. The command had no effect. www.ibm.com/support.
CAC00223W MAX SERVICE INFO ENTRIES IN CAC00407E OPEN ERROR, UNKNOWN RECFM.
USE.
Explanation: An internal Sequential I/O error has
Explanation: This message is in response to a SET been detected. Contact IBM Technical Support at
operator command. You are attempting to define www.ibm.com/support.
another SERVICE INFO ENTRY definition and have
reached the limit on the number of services that can be
CAC00408E SEQIO ERROR nnnnnnn.
defined. Currently, only 32 SERVICE INFO ENTRY
definitions can be defined/active within a data or Explanation: An internal Sequential I/O error has
enterprise server. It adds a new SERVICE INFO ENTRY been detected in file nnnnnnn. A file control block is
definition you must remove one of the existing dumped for problem determination. Contact IBM
SERVICE INFO ENTRY definitions. Technical Support at www.ibm.com/support.
6 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 2. General messages (00000000–0000FFFF)
This section contains general messages, which are in the range 00000000–0000FFFF
(0–65535).
0x000B0003 (720899) An internal error has been 0x000B001B (720923) SAS/C LOCALE initialization
detected. failed.
Explanation: The query processor (QP) service has Explanation: Initialization of SAS/C LOCALE was
encountered an internal error that prevents it from unable to complete. Contact IBM Technical Support at
processing the statement. The statement is ignored and www.ibm.com/support.
processing will continue with the next statement.
Determine whether the statement is valid. Record the
0x000B0024 (720932) SQLDA too small.
statement that caused the error. Then contact IBM
Technical Support at www.ibm.com/support. Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x000B000C (720908) The query processor received an
unexpected message type. 0x000B0040 (720960) Unable to load RRS interface.
Explanation: The client request is unknown to the Explanation: Contact IBM Technical Support at
server. The request is ignored. Contact IBM Technical www.ibm.com/support.
Support at www.ibm.com/support.
0x000B0041 (720961) RRS begin context call failed.
0x000B000E (720910) The query processor received a
request for unsupported functionality. Explanation: Contact IBM Technical Support at
www.ibm.com/support.
Explanation: The client requested a function of the
query processor service that has not yet been
implemented. Contact IBM Technical Support at 0x000B0042 (720962) RRS set context call failed.
www.ibm.com/support. Explanation: Contact IBM Technical Support at
www.ibm.com/support.
0x000B0010 (720912) An entry with this session ID
was not found. 0x000B0043 (720963) RRS express UR interest call
Explanation: An internal error corrupted the session failed.
identifier for the query processor (QP) service. Contact Explanation: Contact IBM Technical Support at
IBM Technical Support at www.ibm.com/support. www.ibm.com/support.
0x000B0013 (720915) Invalid column or parameter 0x000B0044 (720964) RRS set syncpoint control call
information received from client. failed.
Explanation: The data type specified in an SQLDA is Explanation: Contact IBM Technical Support at
unknown. www.ibm.com/support.
0x000B0016 (720918) Query processor memory limit 0x000B0045 (720965) RRS prepare to commit agent
exceeded. call failed.
Explanation: Internal memory limits have been Explanation: Contact IBM Technical Support at
exceeded. Break the select statement into multiple www.ibm.com/support.
statements that each return a subset of the desired data.
12 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 5. API-F error messages 00120000–0012FFFF
(1179648–1245183)
This section contains the API-F error messages, which are in the range
00120000–0012FFFF (1179648–1245183).
0x00120002 (1179650) Data source not found. 0x0012000F (1179663) Successful completion.
Explanation: All data source sessions are in use on all Explanation: Informational message. No action is
instances. You can take any or all of the following required.
actions:
v Wait for sessions to disconnect 0x00120010 (1179664) Resource text for message code
v Increase the maximum number of instances 0x%081x not found.
(SERVICE INFO ENTRY field 5)
Explanation: Internal error. Contact IBM Technical
v Increase the maximum number of sessions Support at www.ibm.com/support.
(SERVICE INFO ENTRY field 6)
0x00120008 (1179656) SQL statement does not accept 0x00120016 (1179670) Session handle invalid.
parameter markers.
Explanation: Internal error. Contact IBM Technical
Explanation: An invalid parameter list was passed for Support at www.ibm.com/support.
an embedded SQL statement. This is due to improper
precompilation. Contact IBM Technical Support at
www.ibm.com/support. 0x00120017 (1179671) No DATA SOURCE definition
found in configuration.
0x00120009 (1179657) Results failed to decode. Explanation: An invalid parameter list was passed for
an embedded SQL statement. This is due to improper
Explanation: The results of the query failed to decode precompilation. Contact IBM Technical Support at
due to either a memory allocation error or an internal www.ibm.com/support.
structural inconsistency. Attempt to execute the SQL
statement again. If the error persists, contact IBM
Technical Support at www.ibm.com/support. 0x00120018 (1179672) CAC_CONFIG is not defined.
Explanation: This error has the following implication
0x0012000C (1179660) Memory allocation has failed. depending on the platform:
v AIX®: The CAC_CONFIG environment variable has
Explanation: Internal error. Contact IBM Technical
not been defined, the pathname that the variable
Support at www.ibm.com/support.
points to does not exist, or there is a syntax error in
the file pointed to by the variable.
v Windows®: The registry has not been set up properly
for the client to execute.
14 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 6. JDBC error messages (001300001–0013000B)
This section contains the JDBC error messages, which are in the range
001300001–0013000B (1245184–1245195).
0x00130002 (1245186) JDBC send error. 0x0013000B (1245195) JDBC disconnect error.
Explanation: Contact IBM Technical Support at Explanation: The disconnect failed. Contact IBM
www.ibm.com/support. Technical Support at www.ibm.com/support.
0x00130003 (1245187) JDBC receive error. 0x0013000C (1245196) Codepage load error.
Explanation: Contact IBM Technical Support at Explanation: The code page specified may not be
www.ibm.com/support. supported by the Java™ Runtime Environment (JRE).
Please check your JRE documentation for information
about the code pages that are supported.
0x00130004 (1245188) JDBC connection failed.
Explanation: Either the data server is not running, or
0x0013000D (1245197) String encoding error.
the data server cannot connect to the data source.
Check the data source and communication Explanation: Either an incorrect code page is being
configuration. used, or there is at least one character in the data that
does not have an equivalent in the server code page.
0x00130005 (1245189) Client session rejected.
0x0013000E (1245198) String decoding error.
Explanation: Check the data source name defined on
the data server, correct if necessary, and try again. Explanation: Either an incorrect code page is being
Otherwise, determine whether or not limit on users and used, or there is at least one character in the data that
threads on the data server is reached. does not have an equivalent in Unicode.
0x00130007 (1245191) JDBC error binding connection. 0x0013000F (1245199) Graphic data encoding error.
Explanation: Check the data source name defined on Explanation: Either an incorrect code page is being
the data server and try again. Otherwise, determine used, or there is at least one character in the data that
whether the limit on users and threads on the data does not have an equivalent in the server code page.
server is reached.
0x0013000G (1245200) Graphic data decoding error.
0x00130008 (1245192) An invalid URL was passed to
Explanation: Either an incorrect code page is being
the JDBC driver.
used, or there is at least one character in the data that
Explanation: The URL passed to the JDBC client was does not have an equivalent in Unicode.
incorrect. Specify the correct URL and resubmit.
0x00420009 (4325385) B-tree read block error. 0x00420013 (4325395) B-tree file write error.
Explanation: Internal error. Contact IBM Technical Explanation: Unable to extend the B-tree file, possibly
Support at www.ibm.com/support. because the LD TEMP SPACE has been exhausted.
0x0042000A (4325386) B-tree key not found. 0x00420014 (4325396) B-tree file read error.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x0042000B (4325387) B-tree write block error. 0x00420015 (4325397) B-tree file seek error.
Explanation: Internal error. Contact IBM Technical Explanation: Unable to extend the B-tree file, possibly
Support at www.ibm.com/support. because the LD TEMP SPACE has been exhausted.
0x0042000C (4325388) B-tree new block write error. 0x00420016 (4325398) B-tree file flush error.
Explanation: The LD TEMP SPACE size needs to be Explanation: Unable to extend the B-tree file, possibly
increased. because the LD TEMP SPACE has been exhausted.
0x0042000D (4325389) B-tree node split error. 0x00420017 (4325399) B-tree file close error.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00430014 (4390932) An unexpected record type was 0x0043001E (4390942) The message prepared for the
found in the change capture messages. distribution service is larger than the
allocated communications buffer.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support with data server Explanation: A committed change record is ready to
output and configuration files. be sent to the distribution service (specifically the
publication service). The change record data is larger
than the maximum size for a communications buffer.
0x00430018 (4390936) Invalid data detected converting
The data server and related components go into
a column value to SQL format.
recovery mode as a result of this error.
Explanation: This error can be caused by invalid data
Contact IBM Technical Support at
in the database. It also can be caused by a data
www.ibm.com/support for assistance.
mapping error.
To resolve data mapping errors:
0x0043001F (4390943) The communications buffer for
v Verify that the data mapping is correct. change capture messages is smaller than
v Check to see if the data being mapped has multiple the B-tree input data buffer size.
redefinitions. If it does, you need to create multiple
Explanation: This is an internal error. Contact IBM
mappings, one for each variation, and then
Technical Support at www.ibm.com/support.
implement the record selection exit (CACRCSEL) to
filter out the changes to the table (versions) that do
not match the data.
24 DB2 II System Messages for Classic Federation and Classic Event Publishing
calls. This may be an application programming error or
0x00430020 (4390944) Segment not found in DBD.
an internal tracking error by the correlation service.
Table Name: Table-NameDBD Name:
DBD-NameSegment Name: Segment-Name Ensure that the IMS application is issuing valid ROLS
calls. If it is, contact IBM Technical Support at
Explanation: This error message is issued during
www.ibm.com/support. Recovery is required.
correlation service initialization processing. The
segment named Segment-Name mapped in table
Table-Name for DBD DBD-Name does not exist in the 0x00430024 (4390948) Error occurred when
DBD load module referenced by the correlation decompressing an element in a data
service’s DBDLIB DD statement. You have mapped the capture log record.
table against a different version of the DBD than the Data element is: Element-Type
correlation service is referencing. Failure reason: return-code
Log record length: length
Ensure that the same DBD that you mapped against is
Current offset: offset
the same DBD that the correlation service is
Computed end: end-offset
referencing. Also ensure that this is the same version of
the DBD that IMS is using.Recovery is not required. Explanation: A hardware decompress error was
reported when attempting to decompress an element of
a Data Capture log record. This is an internal error.
0x00430021 (4390945) Data capture segment
Contact IBM Technical Support at
information received. The segment does
www.ibm.com/support.
not exist in the DBD that the correlation
service is referencing. The additional diagnostic information contained in this
DBD Name: DBD-Name log record identifies the type of data element that the
Segment Name: Segment-Name decode failure occurred on. The return code is the
Data element is: Element-Type value reported by CSRCESRV and is one of the
Log record length: length following values:
Current offset: offset v 4: Output buffer size too small.
Computed end: end-offset
v 8: Data could not be decompressed because a new
Explanation: A data capture log record was received compression method was used.
for a DBD that is being monitored for changes. The v 12: The input and/or output buffer length was a
version of the DBD that the correlation service is negative number.
referencing, however, does not match the DBD that IMS
is using. v 16: Input data is malformed.
Ensure that the proper DBD load module is referenced Also displayed is the total length of the log record
by the correlation service. being decoded, the current offset within the log record
It is also possible that this error may be received when where the data element header starts, and the
log record decoding fails. Additional diagnostic computed end of the data portion of the log record.
information included in this record includes the data Recovery is required.
element header name that the error was found in.
Also included is the length of the log record, the offset 0x00430026 (4390950) Data capture log record data
of the data element header being processed, and the element sequence error.
computed ending offset of the data portion of the log Data element is: Element-Type
record. Recovery is required. Log record length: length
Current offset: offset
Computed end: end-offset
| 0x00430022 (4390946) Error occurred accessing the
| IMS DBD library. Explanation: While decoding a Data Capture log
| DBD Name: DBD-Name record, the correlation service detected a sequence error
for a Data Element within the Data Capture log record.
| Explanation: The DBD identified by DBD-Name does This is an internal error. Contact IBM Technical Support
| not exist in the data sets referenced by the DBDLIB DD at www.ibm.com/support.
| statement in the server JCL. Ensure that the correct
| DBD libraries are referenced and restart the server. Diagnostic information included in this log record
includes the data element header name in which the
error was found.
0x00430023 (4390947) Unknown ROLS token
received. ROLS Token: ROLS-Token Also included is the length of the log record, the offset
of the data element header being processed, and the
Explanation: An IMS application issued a ROLS call; computed ending offset of the data portion of the log
however, the ROLS-Token supplied on the call does not record. Recovery is required.
match any of the tokens issued in previous SETS/SETU
26 DB2 II System Messages for Classic Federation and Classic Event Publishing
| 0x0043002D (4390957) UOR in-flight when 0x0043002F (4390959) Lost or out-of-sequence log
| change-capture agent terminated. buffer condition detected.
| IMS Sub-SystemID: IMS IMS Sub-SystemID: IMS
| Sub-System-Identifier Sub-System-Identifier
| Job Name: Job-Name Job Name: Job-Name
| Job Number: Job-Number Job Number: Job-Number
| ASID: ASID ASID: ASID
| Recovery Token: Recovery-Token Previous Buffer End:
| Data Capture Records: Record-Count High.-Low-Sequence-Numbers
This Buffer Start: High.-Low-Sequence-
Explanation: This message is issued when an IMS
Numbers
change-capture agent notifies the correlation service
End: High.-Low-Sequence-Numbers
that the IMS Logger Exit was called with a termination
function code. The IMS region identified by Explanation: The correlation service has detected that
| IMS-Sub-System-Identifier, Job-Name, Job-Number (or a log buffer has been lost or received out-of-sequence
started task number) and ASID has ended (either for the IMS change-capture agent identified by
normally or abnormally). | IMS-Sub-System-Identifier, Job-Name, Job-Number (or
started task number) and ASID. The Previous Buffer
At the time of termination the correlation service was
End log record sequence number pair identifies the log
in the process of tracking the progress of the UOR
record sequence number previously received from the
identified by Recovery-Token. Record-Count identifies
identified IMS change-capture agent. This Buffer Start
how many Data Capture log records had been found in
and End log record sequence number pairs identify the
the UOR. Recovery is required.
starting and ending log record sequence number pairs
just received.
Note: In addition to logging this error, WTO message
CAC02009E was also issued notifying the The error condition was detected because the starting
operator that an abnormal situation has been sequence number for the just-received log buffer is not
| detected. If the IMS active change-capture agent one greater than the ending sequence number pair
that just terminated was a batch job and when received in the previous buffer. This error is not
the IMS Logger Exit was called and indicated generated when the correlation service detects a
that a batch abend occurred, the correlation rollover of the high-order full word of the log record
service automatically issued a rollback for any sequence number from the previous buffer received.
UOR that was in progress and no WTO message When this condition occurs, the correlation service
is generated or logged. assumes that this is a normal condition and that the
next buffer received will be in sequence. Recovery is
required.
| 0x0032002E (4390958) UOR in-flight when correlation
| service was shut down.
Warning: In addition to logging this error, WTO
| IMS Sub-SystemID: IMS
message CAC02013E is also issued, notifying
| Sub-System-Identifier
the operator that an abnormal situation has
| Job Name: Job-Name
been detected. This is an extremely rare and
| Job Number: Job-Number
potentially dangerous condition that has
| ASID: ASID
been detected and must be attended
| Recovery Token: Recovery-Token
immediately.
| Data Capture Records: Record-Count
Explanation: This message was issued when the It is possible that an initial log buffer was lost or an
correlation service terminated processing (either out-of-sequence condition occurred on log record
normally or abnormally). At the time of termination, sequence number rollover, and, in this case,
the correlation service was tracking the progress of the out-of-sequence UOR(s) may have been successfully
| UOR identified by IMS-Sub-System-Identifier, Job-Name, committed and forwarded to the publication service. It
Job-Number (or started task number), ASID and is possible that there were committed UOR(s) in the
Recovery-Token. Record-Count identifies how many Data first log buffer that should have been propagated
Capture log records had been found in the UOR. before the one(s) that have been forwarded to the
Recovery is required. publication service.
28 DB2 II System Messages for Classic Federation and Classic Event Publishing
the Data Capture options to support the mapping that
0x00430040 (4390976) Unknown type 99 data capture
you have created, or delete Column(s) from the
log record sub-code encountered.
mapping for the segment in error.Recovery is not
required. | Explanation: Error message issued when the
| correlation service receives an unknown type 99 data
| capture record. Associated with this message is a
0x00430035 (4390965) Type 99 error record received.
| binary dump of the IMS log record. Contact IBM
Explanation: IMS reported that creation of a Data | Technical Support at www.ibm.com/support.
Capture log record failed. The IMS documentation
states that the change may have been lost.
0x00430042 (4390978) Unknown processing function
Contact IBM Technical Support at received from change-capture agent.
www.ibm.com/support.Recovery is not possible.
| Explanation: Error message issued when an IMS
| change-capture agent sent an unknown data gram to
0x00430036 (4390966) Unexpected log record received | the correlation service. Associated with this message is
from change-capture agent. | a binary dump of the IMS change capture header.
| Contact IBM Technical Support at
Explanation: The correlation service received a log | www.ibm.com/support.
record that it does not support. Contact IBM Technical
Support at www.ibm.com/support. Recovery is
required. 0x00430043 (4390979) Error-Code Error accessing the
requested DBD.
0x00430037 (4390967) IMS log record being processed | Explanation: Error message issued during correlation
when decoding error detected. | service initialization processing attempting to obtain
| physical DBD information for an IMS table marked for
Explanation: An error was detected while decoding | change capture. Error-Code is one of the following
the contents of a Data Capture log record. The | values that identifies the type of error that was
preceding message in the log identifies the type of | encountered:
decode failure that was detected.
| v BLDL return code is X(Return-Code) for DBD
To assist in problem determination, this message | DBD-Name
dumps the contents of the log record for which the | v GETMAIN return code is X(Return-Code) for DBD
error is being reported. Contact IBM Technical Support | DBD-Name
at www.ibm.com/support. Recovery is required.
| v LOAD return code is X(Return-Code) for DBD
| DBD-Name
0x00430038 (4390968) Data capture log record does
not contain double word sequence Contact IBM Technical Support at
numbers. www.ibm.com/support.
Explanation: You are attempting to use change
capture with an unsupported release of IMS. Change 0x00430048 (4390984) IMS user data.
capture is only supported for IMS Version 7 or later.
| Explanation: Informational message that is generated
| when the trace level is set to 1. Associated with this
0x00430039 (4390969) Committed IMS UOR not | message is a binary dump of the IMS user data that is
found in internal control blocks. | associated with a change event. For a description of the
| Explanation: Error message issued during IMS-specific | user data associated with an event, see IBM DB2
| commit processing. Associated with this message is the | Information Integrator Operations Guide for Classic Event
| UOR identifier that could not be found in the | Publishing.
| correlation service internal control blocks that track IMS
| committed UORs before they are sent to the 0x00430049 (4390985) IMS committed UOR staged.
| distribution service for processing. Contact IBM
| Technical Support at www.ibm.com/support. | Explanation: Informational message that is generated
| when the trace level is less than 3. Identifies that the
| correlation service has determined that an IMS UOR
0x0043003A (4390970) Invalid sync-point log record | has been committed. Associated with this message is a
sequence encountered. Change-capture | binary dump for the event capture header associated
agent, UOR and sync-point diagnostic | with the UOR.
information follows.
Explanation: Contact IBM Technical Support at
www.ibm.com/support.
30 DB2 II System Messages for Classic Federation and Classic Event Publishing
v Commit-Count: Identifies the total number of v IMS-Event-Count: Summary total of the following
committed UORs that contain data capture records types of IMS events.
that the correlation service has received from all IMS v Cascade-Delete-Count: Number of CASC
Logger Exit instances. CALL_FUNCTIONS processed for this DBD.
v Rollback-Count: Identifies the total number of UORs v Delete-Count: Number of DLET CALL_FUNCTIONS
that were rolled back either explicitly by the processed for this DBD.
application, or implicitly by IMS.
v DLLP-Count: Number of DLLP CALL_FUNCTIONS
v Read-Only-Count: Identifies the total number of UORs processed for this DBD.
processed by the correlation service that did not
v Insert-Count: Number of ISRT CALL_FUNCTIONS
contain any Data Capture log records. These may be
processed for this DBD.
true read-only UORs, or may have contained updates
for DBDs that are not being monitored. v Replace-Count: Number of REPL CALL_FUNCTIONS
processed for this DBD.
v Processed-Count: Identifies the total number of
committed UORs that have been processed and that
had their events forwarded to the publication service. 0x00430051 (4390993) Segment monitoring
v IMS-Event-Count: Summary total of the following information.
types of IMS events. DBD name: DBD-Name
Segment name: Segment-Name
v Cascade-Delete-Count: Number of CASC
Parent segment: Parent-Segment-Name
CALL_FUNCTIONS processed.
Hierarchic level: Level-number
v Delete-Count: Number of DLET CALL_FUNCTIONS Maximum length: Maximum-Length
processed. Key length: Key-Length
v DLLP-Count: Number of DLLP CALL_FUNCTIONS Key offset: Key-Offset
processed. DLET/ISRT/REPL: Standard-Data-Capture-
v Insert-Count: Number of ISRT CALL_FUNCTIONS Options
processed. Cascade delete: Cascade-Delete-Data-
Capture-Options
v Replace-Count: Number of REPL CALL_FUNCTIONS
Number of tables: Table-Count
processed.
Number of events: IMS-Event-Count
Number of CASC events:
0x00430050 (4390992) DBD monitoring information. Cascade-Delete-Count
DBD name: DBD-Name Number of DLET events: Delete-Count
Number of segments: Segment-Count Number of DLLP events: DLLP-Count
Version length: Length Number of ISRT events: Insert-Count
Version identifier: DBD-Version-Identifier Number of REPL events: Replace-Count
Number of events: IMS-Event-Count
Explanation: Informational log message generated
Number of CASC events:
when the trace level is less than 4. One of these
Cascade-Delete-Count
messages is generated for each segment in a DBD being
Number of DLET events: Delete-Count
monitored.
Number of DLLP events: DLLP-Count
Number of ISRT events: Insert-Count This message contains information extracted from the
Number of REPL events: Replace-Count physical DBD and summary processing statistics. The
following information is displayed:
Explanation: Informational log message generated
when the trace level is 4 or less. One of these messages v DBD-Name: The name of the DBD.
is generated for each DBD being monitored. v Segment-Name: The name of the segment.
This message contains information extracted from the v Parent-Segment-Name: The parent segment name or
physical DBD and summary processing statistics. The ‘(none)’, for root segments.
following information is displayed: v Level-Number: The segment’s hierarchic level in the
v DBD-Name: Name of the DBD being monitored. database.
v Segment-Count: The number of segments contained in v Maximum-Length: The segment’s length. For a
the DBD. variable length segment this represents its maximum
length.
v Length: The length of the DBD version identifier.
v Key-Length: The length of the segment sequence field,
v DBD-Version-Identifier: The actual DBD version
or zero if the segment does not have a sequence
identifier. The version identifier is compared against
field.
the DBD version identifier contained within the Data
Capture log records to ensure that the correlation v Key-Offset: The segment’s relative-1 starting offset of
service is using the same DBD that IMS is using. the sequence field in the segment. Zero if the
segment does not have a sequence field.
32 DB2 II System Messages for Classic Federation and Classic Event Publishing
| v UOR-Start: Identifies the IMS log record that | – DLLP-Count: Number of DLLP
| represents the start of the UOR. UOR-Start consists | CALL_FUNCTIONS processed for this UOR.
| of a 16-hexadecimal digit system clock value (that | – Insert-Count: Number of ISRT CALL_FUNCTIONS
| was used to generate the DB2-Timestamp value) and | processed for this UOR.
| the IMS log record sequence number (in hexadecimal
| – Replace-Count: Number of REPL
| format) for the IMS type 99 data capture log record
| CALL_FUNCTIONS processed for this UOR.
| that caused the start of this UOR to be detected.
0x00430059 (4391001) IMS UOR sync-point log record 0x0043005D (4391005) Combining IMS data capture
tracking control block. log records.
| Explanation: Error message generated when an error | Explanation: Informational message that is generated
| is detected by the correlation service while processing a | when the trace level is less than 2. This message is
| committed IMS UOR. Associated with the message is a | issued when the correlation server detects that an IMS
| hexadecimal dump of summary information about an | type 99 data capture log record has spanned IMS
| IMS sync-point control record associated with the UOR | physical log records. The correlation service needs to
| that is in error. Contact IBM Technical Support at | combine the physical log records into logical segments
| www.ibm.com/support. | that can be decoded during commit processing.
| This message identifies a portion of an existing
0x0043005A (4391002) IMS change-capture agent | spanned log record that currently cannot be processed.
sync-point log record tracking control | The physical contents of the partial log record are
block. | dumped when this message is issued. After this
| message is issued, you receive message 0x0043004E
| Explanation: Error message generated when an error | (4390990) that dumps the contents of the log record
| is detected by the correlation service while processing a | with which the partial element is being combined.
| committed IMS UOR. Associated with the message is a
| hexadecimal dump of a sync-point tracking record
| associated with the IMS change-capture agent of the
| UOR that is in error. Contact IBM Technical Support at
| www.ibm.com/support.
34 DB2 II System Messages for Classic Federation and Classic Event Publishing
| when the trace level is less than 3. Identifies the start of
| 0x0043005E (4391006) IMS data capture header
| an CA-IDMS run-unit for which:
| information. FLAGS(Flag1,
| Flag2),LOG_DATA_OFFSET(Starting | v UOR-ID consists of the CA-IDMS run-unit identifier
| Offset),COMPR_ALGORITHM(Type) | with an Event Publisher generated sequence number
| appended (for run-units that contain multiple
| Explanation: Informational message that is generated | commits).
| when the trace level is less than 2. Identifies the
| v IDMS-CCA-Name identifies the CA-IDMS
| contents of the data capture header for an IMS type 99
| change-capture agent from which the run-unit
| data capture log record being decoded during commit
| originated.
| processing. For a description of the contents of the data
| capture header, see IMS Customization Guide. | v Journal-Sequence-Number identifies the journal record
| sequence number (in hexadecimal format) of the
| CA-IDMS TIME record associated with the start of
| 0x0043005F (4391007) IMS data element header | the run-unit.
| information. LOGID(Element-Header-
| v Journal-Timestamp identifies journal date and time
| ID),LOG_FLAGS(Element-Header-
| stamp (in hexadecimal format) of the CA-IDMS
| Flags),LOG_LL(Element-
| TIME record associated with the start of the run-unit.
| Length),Offset(Log-Record-Offset)
| Explanation: Informational message that is generated
| 0x004300B3 (4391091) IDMS run-unit ended.
| when the trace level is less than 2. Identifies the
| UOR Identifier: UOR-ID
| contents of a date element header contained in an IMS
| CCA Identifier: IDMS-CCA-Name
| type 99 data capture log record being decoded during
| Start Sequence Number:
| commit processing.
| Journal-Sequence-Number
| For descriptions of the contents of the LOGID, | Start Timestamp: Journal-Timestamp
| LOG_FLAGS and LOG_LL components of the data | Disposition: Disposition
| element header, see IMS Customization Guide. The
| Explanation: Informational message that is generated
| Log-Record-Offset identifies the current offset of the data
| when the trace level is less than 3. Identifies that a
| component for the data element header in the IMS log
| CA-IDMS run-unit has completed for which:
| record being processed.
| v UOR-ID consists of the CA-IDMS run-unit identifier
| with an Event Publisher generated sequence number
0x00430090 (4391056) User not found. | appended (for run-units that contain multiple
Explanation: Contact IBM Technical Support at | commits).
www.ibm.com/support. | v IDMS-CCA-Name identifies the CA-IDMS
| change-capture agent from which the run-unit
| originated.
0x004300A0 (4391072) After image records found
without a corresponding before image | v Journal-Sequence-Number identifies the journal record
| sequence number (in hexadecimal format) of the
Explanation: Updated record images were found | CA-IDMS TIME record associated with the start of
without a corresponding before image. This is usually | the run-unit.
caused by selecting the starting point for the VSAM
| v Journal-Timestamp identifies journal date and time
agent when CICS® is active and that time is in the
| stamp (in hexadecimal format) of the CA-IDMS
middle of a unit of work.
| TIME record associated with the start of the run-unit.
| v Disposition identifies the status of the run-unit with
| 0x004300B0 (4391088) IDMS change-capture agent | one of the following values:
| started. CCA identifier: IDMS-CCA-Name | – Run-Unit committed.
| Explanation: Informational message that is generated | – Run-Unit rolled back.
| when the trace level is less than 3. Identifies the start of | – Run-Unit discarded - agent shutdown.
| an CA-IDMS change-capture agent identified by | – Run-Unit discarded - recovery started.
| IDMS-CCA-Name. | – Run-Unit discarded - recovery completed.
| – Internal error
| 0x004300B2 (4391090) IDMS run-unit started. | In subsequent executions of the IDMS recovery
| UOR Identifier: UOR-ID | change-capture agent, the final outcome of the
| CCA Identifier: IDMS-CCA-Name | discarded run-unit will either be Run-Unit committed
| Start Sequence Number: | or rolled back.
| Journal-Sequence-Number
| Start Timestamp: Journal-Timestamp
| Explanation: Informational message that is generated
36 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 11. Change-capture agent error messages
(00440000–0044FFFF)
This section contains the change-capture agent error messages, which are in the
range 00440000–0044FFFF (4456448–4521983).
0x00440001 (4456449) Unable to locate task identifier. 0x00440034 (4456500) Connect to logstream failed.
Explanation: Internal error. Contact IBM Technical Explanation: A connect to a log stream failed. Check
Support at www.ibm.com/support. the return code and reason codes for the IXGCONN
macro.
0x00440002 (4456450) The SERVICE INFO ENTRY
pointer is NULL. 0x00440035 (4456501) Query to logstream failed.
Explanation: Internal error. Contact IBM Technical Explanation: A query to a log stream failed. Check the
Support at www.ibm.com/support. return code and reason codes for the IXGQUERY
macro.
0x00440030 (4456496) A logstream was not specified
or is invalid 0x00440036 (4456502) Start to logstream failed.
Explanation: A log stream was not specified on field Explanation: A start to a log stream failed. Check the
10 of the SERVICE INFO ENTRY for the CICS VSAM return code and reason codes for the IXGBRWSE
agent, only one log stream was specified, or more than macro.
two log streams were specified and the Log of Logs log
stream was not one of them.
0x00440037 (4456503) Browse to logstream failed.
Explanation: A browse to a log stream failed. Check
0x00440031 (4456497) Start date was not specified or
the return code and reason codes for the IXGBRWSE
is invalid
macro.
Explanation: A start option of TIME was specified on
field 10 of the SERVICE INFO ENTRY for the CICS
0x00440039 (4456505) No system log specified.
VSAM agent, but the date specified was not a valid
date. Explanation: A system log stream was not specified in
field 10 on the SERVICE INFO ENTRY for the CICS
Specify a valid start date and restart the CICS VSAM
VSAM Agent
Agent.
38 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 12. Query processor finite state machine error
messages (00490001–00490009)
This section contains the query processor finite state machine error messages,
which are in the range 00490001–00490009 (4784129–4784137) .
0x004D0002 (5046274) Load of system exit failed. 0x004D0015 (5046293) WLM call failed.
Explanation: Contact IBM Technical Support at Explanation: A WLM call issued by the WLM Exit has
www.ibm.com/support. failed. Review the data server JES JCL log for the
return code and reason codes that were returned on the
failing call.
0x004D0005 (5046277) Memory allocation failed.
Explanation: Increase MESSAGE POOL SIZE.
0x004D0016 (5046294) The PSB name plus prefix
could not be RACF verified.
0x004D0007 (5046279) The system exit environment
Explanation: The PSB Name plus the prefix exceeds 8
has been corrupted.
bytes, therefore, RACF® authorization cannot be
Explanation: User exit error checking has found a performed.
problem in the environment. Contact IBM Technical
Support at www.ibm.com/support.
0x004D0017 (5046295) Stored procedure access
denied.
0x004D0008 (5046280) Exit name missing or invalid.
Explanation: The SAF Exit is active with the
Explanation: Contact IBM Technical Support at subparameter SPCLASS. Your user ID is either invalid
www.ibm.com/support. or not allowed to execute the stored procedure.
Another reason could be that the stored procedure is
not defined in the class that is specified for SPCLASS.
0x004D000F (5046287) Invalid keyword specified. Processing of the query is terminated. Contact IBM
Explanation: An exit parameter keyword is invalid. Technical Support at www.ibm.com/support to resolve
Contact IBM Technical Support at the problem.
www.ibm.com/support.
0x004D0018 (5046296) Load failed for the DB2 thread
0x004D0010 (5046288) Missing keyword or keywords. management exit.
Explanation: An exit parameter keyword is missing. Explanation: The load of the DB2 Thread
Contact IBM Technical Support at Management Exit program failed. Check the server log
www.ibm.com/support. for the name of the failing exit and verify the module
exists in a library concatenated to the server’s STEPLIB.
This name should match the name specified in field 10
0x004D0013 (5046291) CPU time exceeded. of the Service Info Entry for the DB2 CAF service.
Explanation: The CPU Resource Governor Exit is
active. The query being executed exceeded the time 0x004D0019 (5046297) The DB2 thread management
limit set on the CPU GOVERNOR configuration exit returned a nonzero return code.
parameter. Processing of the query is terminated.
Contact IBM Technical Support at Explanation: A call to the DB2 Thread Management
www.ibm.com/support to resolve the problem. Exit program returned a nonzero return code indicating
an exit specific failure. Check the server log for the
actual return code issued by the exit. The return codes
0x004D0014 (5046292) Access denied. for the delivered sample are documented in the
Explanation: The SAF Exit is active. Your user ID is CACSX07 source code (found in the SCACSAMP
either invalid or not allowed to access a file or IMS library). The name of the exit you are running can be
referenced by one of the tables in the query you were found in field 10 of the Service Info Entry for the DB2
executing. Processing of the query is terminated. CAF service.
Contact IBM Technical Support at
www.ibm.com/support to resolve the problem.
42 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 14. Common CA-Datacom interface error messages
(00540000-0054FFFF)
This section contains the common CA-Datacom interface error messages, which are
in the range 00540000-0054FFFF (5505024-5670559).
44 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 15. Server error messages (00550000–0055FFFF)
This section contains the server error messages, which are in the range
00550000–0055FFFF (5570642–5570679).
The ODBC/CLI client reports error conditions as formatted messages. You can
retrieve error message text by using the ODBC/CLI SQLGetDiagRec or
SQLGetDiagField functions. The ODBC/CLI client can report either error
conditions that it detects or error conditions that occurred on the data server.
Regardless of the source of the error condition, the format of the error messages
generated by the ODBC/CLI client is:
[IBM DB2 II][ODBC/CLI Driver][Data Server][API Name-Message text]
v [IBM DB2 II CF] indicates that DB2 Information Integrator Classic Federation or
Classic Event Publisher is reporting the error.
v [ODBC/CLI Driver] indicates that the ODBC/CLI client component issued the
error.
v [Data Server] is displayed only when the error condition was detected or
reported by the data server.
v [API Name] identifies the name of the ODBC/CLI API that was called when the
error condition was detected or reported.
v [Message text] provides information about the error condition that is being
reported.
The format of the [Message text depends on whether the error code represents a
DB2 Universal Database SQLCODE (a negative number) or other error conditions
(a positive value).
For all other error conditions, the message text consists of two or three distinct
segments.
v The first segment of the message text identifies the hexadecimal representation
of the error message being reported. The format used is Error code XXXXXXXX,
where XXXXXXXX is the message identification number.
v The second segment of the message text describes the error condition.
v The third segment of the message text is additional information that is specific
to the error condition. It is included only when additional information is
available. Additional information can be appended to the text description when
the connection to the data server fails, when extra diagnostic information is
returned for the error condition that is being reported, or when the descriptive
text ends with a semicolon.
When a data server connection fails, data source URL information is appended to
the end of the message text in the format DSN:Data-Source-Name/Protocol-String.
When the descriptive text ends with a semicolon, then additional information that
is specific to this error condition follows the message text.
The rest of this chapter provides a list of error and information messages that can
be detected and reported by the ODBC/CLI client.
v The error message number is shown in both hexadecimal and decimal formats.
The identification portion of the message text that is formatted by the
ODBC/CLI client is always shown in hexadecimal format. On Windows systems,
the error reporting tool that you use might also display the decimal version of
the number.
v The ODBC/CLI SQLSTATE code that is associated with the error that is being
reported by the ODBC/CLI client is also shown. In Microsoft® ODBC driver
documentation, several of the ODBC/CLI error message SQLSTATE codes are
identified as being generated by the ODBC Driver Manager (DM).
If you run the ODBC client on Windows systems, you will not receive any of the
error messages that are identified as driver manager reported errors.
If you run the ODBC/CLI client software on UNIX systems, and your
application is not using an ODBC Driver Manager to communicate with the CLI
client, you might receive any of the error messages shown below.
sqlstate: 01000
x00560001 (5636097) Stored procedure output or
input-output parameter did not return a
value for parameter number: x00560010 (5636112) String data, right-truncated.
parameter-number.
Explanation: The right portion of the string was
Explanation: This warning message is returned when truncated. Supply a larger char buffer to prevent
a parameter to a stored procedure is bound as truncation.
OUTPUT or as INPUT/OUTPUT, but the stored
procedure defines the parameter as INPUT. Bind the sqlstate: 01004, 22001
parameter correctly as INPUT.
sqlstate: 01000 x00560011 (5636113) Option value changed.
Explanation: This message is a warning that indicates
x00560002 (5636098) SQLEndTran failed on one or that an option to SQLSetStmtAttr was changed to the
more connections. supported value.
48 DB2 II System Messages for Classic Federation and Classic Event Publishing
x00560013 (5636115) COUNT field incorrect. x00560021 (5636129) Numeric value out of range.
Explanation: Ensure that the number of parameters Explanation: SQL_DECIMAL, SQL_FLOAT,
are set correctly for a statement before you call SQL_INTEGER, or SQL_DOUBLE value is out of range
SQLExecute. when attempting to convert the SQLVAR to a
descriptor.
sqlstate: 07002
sqlstate: 22003
x00560014 (5636116) The statement did not return a
result set. x00560022 (5636130) Invalid character value for cast
specification.
Explanation: SQLDescribeParam returns error for
statements that do not produce a result set. Explanation: A conversion was attempted between
data types that are not compatible. Correct the
sqlstate: 07005
attempted conversion and try again.
sqlstate: 22018
x00560015 (5636117) Invalid descriptor index.
Explanation: A SQLBindCol or a SQLGetDescField
x00560023 (5636131) Invalid cursor state.
was attempted on a invalid descriptor index. Check the
index and attempt the API again. Explanation: The state of the cursor is invalid.
SQLExecute was called on a statement that is already in
sqlstate: 07009
EXECUTE state. SQLFetch was called on a statement
that has not been prepared or opened.
x00560016 (5636118) Session has been rejected.
sqlstate: 24000
Explanation: Either the data source is not defined on
the server as a service, or an authentication failure led
x00560024 (5636132) Autocommit failed.
to a rejected session.
Explanation: The autocommit operation was not
sqlstate: 08001
completed. You must obtain data server diagnostics to
troubleshoot this problem.
x00560017 (5636119) Connection name in use.
sqlstate: 24000
Explanation: A connection was attempted on a handle
that is already connected.
x00560025 (5636133) Invalid transaction state.
sqlstate: 08002
Explanation: SQLDisconnect cannot be issued because
transactions are outstanding on some statements that
x00560018 (5636120) Connection does not exist. are defined on the connection handle.
Explanation: A connection does not exist. Obtain a sqlstate: 25000
connection before attempting the API.
sqlstate: 08003 x00560026 (5636134) Invalid cursor name.
Explanation: SQLSetCursorName failed because the
x00560019 (5636121) Server terminated the cursor name length is not valid. The allowable length
connection. of the cursor name is between one and 30 bytes. Also, a
cursor name cannot start with the value SQLCUR. The
Explanation: Receive from the connection handle prefix SQLCUR is reserved for cursors that the
failed, and the data server terminated the connection. ODBC/CLI driver software generates.
sqlstate: 08S01 sqlstate: 34000
x00560020 (5636128) Indicator variable required but x00560027 (5636135) Duplicate cursor name.
not supplied.
Explanation: SQLSetCursorName has been called with
Explanation: An indicator variable is required because a cursor name that already exists.
the column is nullable, but the indicator variable is not
supplied as a part of the SQLBindParameter or a sqlstate: 3C000
SQLBindCol API.
sqlstate: 22002
50 DB2 II System Messages for Classic Federation and Classic Event Publishing
x0056003d (5636157) No result set description x00560055 (5636181) Invalid use of null pointer.
returned.
Explanation: The data pointer supplied to the API is
Explanation: Internal error. Contact IBM Technical NULL but the driver expects a valid pointer.
Support at www.ibm.com/support.
sqlstate: HY009
sqlstate: HY000
x00560056 (5636182) Function sequence error.
x0056003e (5636158) Unknown SQL data type
Explanation: Function Sequence Error. Ensure that the
received from server: SQL-Type-Code
sequence of the ODBC calls are valid.
Explanation: Internal error. Contact IBM Technical
sqlstate: HY010
Support at www.ibm.com/support.
sqlstate: HY000
x00560057 (5636183) Statement is executing.
Explanation: An SQLDisconnect operation has been
x0056003f (5636159) Unknown SQL statement type.
attempted on a connection where statements are in use.
SQL-Statement-Type.
The state of the statements do not allow a disconnect.
Explanation: Internal error. Contact IBM Technical
sqlstate: HY010
Support at www.ibm.com/support.
sqlstate: HY000
x00560058 (5636184) Statements are in use.
Explanation: An SQLDisconnect operation has been
x00560050 (5636176) Memory allocation failed.
attempted on a connection where statements are in use.
Explanation: Increase the size of the message pool Free the statements before you attempt a disconnect
defined for the ODBC/CLI client. To increase the size operation.
of the message pool, use the parameter
sqlstate: HY010
MESSAGE_POOL_SIZE.
sqlstate: HY001
x00560059 (5636185) Descriptors are in use.
Explanation: An SQLDisconnect operation has been
x00560051 (5636177) Invalid application buffer type.
attempted on a connection when the descriptors
Explanation: SQLBindCol was attempted on an defined on this connection are in use. Free the
unsupported C or application type. descriptors before you attempt a disconnect operation.
sqlstate: HY003 sqlstate: HY010
x00560052 (5636178) Invalid SQL data type. x0056005a (5636186) No result set row position exists.
Explanation: SQLBindCol was attempted with an Explanation: A ResultSet operation has been
unsupported SQL data type. attempted on a cursor that has no result set.
sqlstate: HY004 sqlstate: HY010
x00560053 (5636179) Statement is not prepared. x0056005b (5636187) Invalid transaction operation
code.
Explanation: An attempt was made to access a
descriptor for which the statement has not been Explanation: An SQLEndTran operation has been
prepared. passed a wrong operation code. Valid operations are
SQL_COMMIT or SQL_ROLLBACK. Correct the
sqlstate: HY007
application to pass the correct values.
sqlstate: HY012
x00560054 (5636180) Operation canceled.
Explanation: The operation on the statement was
x0056005c (5636188) Memory management error.
canceled.
Explanation: Internal error. Contact IBM Technical
sqlstate: HY008
Support at www.ibm.com/support.
sqlstate: HY013
Explanation: A Descriptor API was called when the Explanation: An invalid table type was passed to the
descriptor is in an inconsistent state. SQLTables API.
x00560063 (5636195) Invalid attribute value. x00560076 (5636214) Invalid SchemaName parameter.
Explanation: An attempt was made to get or set an Explanation: An invalid table type was passed to the
invalid attribute on a valid handle. SQLTables API.
52 DB2 II System Messages for Classic Federation and Classic Event Publishing
x00560077 (5636215) Invalid TableName parameter. x00560085 (5636229) Scope type out of range.
Explanation: An invalid table name was passed to the Explanation: An SQLSpecialColumns API returns this
SQLTables API. error when the scope is not SQL_SCOPE_CURROW or
SQL_SCOPE_TRANSACTION.
sqlstate: HY090
sqlstate: HY098
x00560078 (5636216) Invalid ColumnName parameter.
x00560086 (5636230) Nullable type out of range.
Explanation: An invalid column name was passed to
the SQLColumns API or to the SQLProcedureColumns Explanation: An SQLSpecialColumns API returns this
API. error when the nullable type is incorrect.
sqlstate: HY090 sqlstate: HY099
x00560079 (5636217) Invalid ProcName parameter. x00560087 (5636231) Uniqueness option type out of
range.
Explanation: An invalid procedure name was passed
to the SQLProcedures API or to the Explanation: An SQLSpecialColumns API returns this
SQLProcedureColumns API. error when the uniqueness option is incorrect.
sqlstate: HY090 sqlstate: HY100
x00560080 (5636224) Invalid descriptor field x00560088 (5636232) Accuracy option type out of
identifier. range.
Explanation: The field identifier value was invalid, or Explanation: An SQLSpecialColumns API returns this
the value was invalid for the type of descriptor that error when the uniqueness option is incorrect.
was passed to the SQLGetDescField API.
sqlstate: HY101
sqlstate: HY091
x00560089 (5636233) Invalid retrieval code.
x00560081 (5636225) Invalid attribute or option
Explanation: An SQLDataSources API returns error
identifier.
when the retrieval code is not SQL_FETCH_FIRST or
Explanation: An invalid attribute or option was SQL_FETCH_NEXT.
passed to the Get or Set calls on the ODBC handles.
sqlstate: HY103
sqlstate: HY092
x0056008a (5636234) Invalid precision or scale.
x00560082 (5636226) Invalid window handle.
Explanation: SQLBindParameter has been passed an
Explanation: An invalid window handle was passed invalid precision or scale.
to the SQLDriverConnect API. Application error.
sqlstate: HY104
sqlstate: HY092
x0056008b (5636235) Invalid parameter type.
x00560083 (5636227) Function type out of range.
Explanation: SQLBindParameter has been passed an
Explanation: An invalid function type was passed to invalid parameter type. Parameter types can only be
the SQLFunctions call that returns TRUE or FALSE, SQL_PARAM_INPUT, SQL_PARAM_OUTPUT or
depending on the function type that was passed to the SQL_PARAM_INPUT_OUTPUT.
call.
sqlstate: HY105
sqlstate: HY095
x0056008c (5636236) Fetch type out of range.
x00560084 (5636228) Column type out of range.
Explanation: SQLFetchScroll does not support the
Explanation: An SQLSpecialColumns API returns this type of fetch orientation that was passed.
error when the Identifier type is not the
sqlstate: HY106
SQL_BEST_ROWID or SQL_ROWVER.
sqlstate: HY097
54 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 17. Connector error messages (00570000–0057FFFF)
This section contains the connector error messages, which are in the range
00570000–0057FFFF (5701632–5767167).
0x00570032 (5701682) Error accessing VSAM catalogs. 0x00570039 (5701689) Cannot establish position
within file (empty).
Explanation: SHOWCAT macro failed. Check the
second four bytes of SQLEXT in the SQLCA for the Explanation: VSAM POINT macro failed because an
return code returned from the SHOWCAT macro. See empty file was detected. Rerun the metadata utility for
IBM MVS/XA VSAM Catalog Administration: Access the table being accessed, specifying a loaded VSAM
Method Services Reference for more information file, and try again. If this does not resolve the problem,
regarding SHOWCAT return codes. If the problem is Contact IBM Technical Support at
not obvious, contact IBM Technical Support at www.ibm.com/support.
www.ibm.com/support.
0x00570042 (5701698) All PCBs are in use.
0x00570033 (5701683) Cannot acquire information
Explanation: Too many cursors have been opened for
about VSAM data set.
the same database. Add additional PCBs to the PSB
Explanation: SVC 99 failed trying to acquire and reassemble the PSB.
information about the status of a VSAM data set. Check
the second four bytes of SQLEXT in the SQLCA for the
0x00570044 (5701700) Cannot access a PCB for the
reason code returned from the SVC 99 call and take
database requested.
appropriate action. See IBM MVS/XA System Macros &
Facilities Volume 1 for more information regarding SVC Explanation: Either all PCBs for the database mapped
99 reason codes. If the problem is not obvious, contact for the table being opened are in use, the PSB is
IBM Technical Support at www.ibm.com/support. defined incorrectly, or the IMS database is empty.
Ensure that the PSB is correctly defined. If the
PCBPREFIX option is being used, ensure that the
PCBPREFIX specified in the metadata grammar
matches the PCBPREFIX used in the PSB. Also, (when
using PCBPREFIX) ensure that the PCBs begin their
sequence numbering with zero (for example,
56 DB2 II System Messages for Classic Federation and Classic Event Publishing
PCBPREFIX=PAYROLL first PCBNAME must be
0x0057004C (5701708) DRA/RRS PSB scheduling
PAYROLL0). If the PCBPREFIX option is not being
failed. See system log from data server.
used, ensure that there is an adequate number of PCBs
referencing the IMS database that the table has been Explanation: If an examination of SYSPRINT does not
mapped against. Add additional PCBs to the PSB and reveal the cause of the failure, contact IBM Technical
reassemble the PSB. Support at www.ibm.com/support.
0x00570045 (5701701) Cannot access a PCB containing 0x0057004D (5701709) PCBPREFIX lookup failed
the required segment(s). using DRA interface. See SYSPRINT
from data server for more information.
Explanation: At least one PCB was found for the
correct database but no PCB was sensitive to all Explanation: If an examination of SYSPRINT does not
segments mapped by the table being accessed. Ensure reveal the cause of the failure, contact IBM Technical
that the PSB is correctly defined. Add additional PCBs Support at www.ibm.com/support.
to the PSB and reassemble the PSB.
0x0057004E (5701710) DRA/RRS PSB unschedule
0x00570046 (5701702) IMS connector memory failed.
allocation failed.
Explanation: Error reported unscheduling a PSB. See
Explanation: The memory that was requested could the data server log for more details.
not be allocated. Increase the size of the MESSAGE
POOL SIZE parameter in the master configuration
0x0057004F (5701711) DRA termination failed. See
member and run the query again.
system log from data server for more
information.
0x00570047 (5701703) Unexpected IMS status code
Explanation: If an examination of SYSPRINT does not
received. See log for more info.
reveal the cause of the failure, contact IBM Technical
Explanation: A DL/I call issued by the IMS SSI Support at www.ibm.com/support.
received an unexpected status code. Check the second
four bytes of the SQLEXT in the SQLCA for the IMS
0x00570051 (5701713) Scheduled PSB(s) contain no
status code returned from the DL/I call. Also examine
usable PCB for the current table.
the data server job output for messages. Change the
VSPEC parameter in the data server to TR to activate Explanation: Verify that the correct PSB was specified
DLITRACE output. Examine the DFSTROUT data set for the query and that it contains a usable PCB. Also
output to identify the DL/I call that is failing. ensure that the correct PCB is not currently in use by
another task. If the failure cannot be resolved, contact
IBM Technical Support at www.ibm.com/support.
0x00570048 (5701704) Attempt to open second cursor
for same HSAM database.
0x00570053 (5701715) DL/I failure while retrieving
Explanation: The application attempted to open more
database segments. See data server log
than one cursor on one or more tables mapped to the
for more information.
same HSAM database. IMS does not support multiple
PCBs for HSAM databases, therefore, the data server is Explanation: If an examination of SYSPRINT does not
forced to reject the request. This restriction only applies reveal the cause of the failure, contact IBM Technical
to HSAM databases. Support at www.ibm.com/support.
0x0057004A (5701706) No PCB with the correct 0x00570054 (5701716) No IMS interface is available.
PROCSEQ.
Explanation: Either the master configuration file for
Explanation: The table definition contains a column the data server did not contain a SERVICE INFO
that references an XDFLD. However, none of the PCBs ENTRY for IMS access or the initialization of the IMS
in the PSB being used by the IMS SSI contains a PCB access service failed. If the configuration contains an
with a PROCSEQ parameter that references the entry for DRA or BMP/DBB access, Check the system
Secondary Index DBD containing the XDFLD. Ensure log from the data server for errors initializing the IMS
that the PSB is properly defined. Add additional PCBs access.
to the PSB and reassemble the PSB.
0x00570057 (5701719) DRA Prepare request failed. Explanation: Contact IBM Technical Support at
See SYSPRINT from data server for www.ibm.com/support.
more information.
Explanation: The PREPARE call issued as part of PSB 0x00570061 (5701729) Error reading the metadata
termination processing in the DRA environment catalog while processing a query
received an error. See the SYSPRINT from the data referencing a system table.
server for more information on the cause of the error. Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x00570058 (5701720) DRA Commit-Terminate
request failed. See SYSPRINT from data 0x00570062 (5701730) Error attempting to open the
server for more information. metadata catalog to process a query
Explanation: The COMMIT/TERMINATE call issued referencing a system table.
as part of the PSB termination processing in the DRA Explanation: Internal error. Contact IBM Technical
environment received an error. See the SYSPRINT from Support at www.ibm.com/support.
the data server on the cause of the error.
58 DB2 II System Messages for Classic Federation and Classic Event Publishing
If you have verified that these are not the cause of the
0x00570070 (5701744) An error occurred in locating
error, contact IBM Technical Support at
the task identifier during IMS
www.ibm.com/support.
initialization.
Explanation: Internal error. Contact IBM Technical
0x00570066 (5701734) CICS error in table close
Support at www.ibm.com/support.
process.
Explanation: This is an internal error. Contact IBM
0x00570071 (5701745) The IMS environment has
Technical Support at www.ibm.com/support.
already been initialized.
Explanation: The master configuration file contains a
0x00570067 (5701735) CICS error retrieving a record.
SERVICE INFO ENTRY for more than one IMS
Explanation: Internal error. Contact IBM Technical environment. The first SERVICE INFO ENTRY is
Support at www.ibm.com/support. processed and all subsequent definitions are failed with
this error message. Remove or comment out any extra
SERVICE INFO ENTRY definitions to clear up this
0x00570068 (5701736) CICS error seeking to a message.
position in the file.
Explanation: Internal error. Contact IBM Technical 0x00570072 (5701746) The IMS region controller
Support at www.ibm.com/support. parameter was not found in the JCL.
Explanation: The IMS region controller start-up
0x00570069 (5701737) CICS error updating a record. parameter was found in the JCL PARM to the data
Explanation: Internal error. Contact IBM Technical server. Check the JCL for the data server and verify
Support at www.ibm.com/support. that an IMS parameter starting with “BMP”, “DBB”, or
“DLI” is present in the PARM= keyword of the EXEC
statement.
0x0057006A (5701738) CICS error inserting a record.
Explanation: Internal error. Contact IBM Technical 0x00570073 (5701747) The DETACH of the IMS
Support at www.ibm.com/support. region controller failed.
Explanation: Internal error. Contact IBM Technical
0x0057006B (5701739) CICS error deleting a record. Support at www.ibm.com/support.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. 0x00570074 (5701748) The ATTACH of the IMS
region controller failed.
0x0057006C (5701740) CICS error releasing a lock on Explanation: The ATTACH macro failed to attach the
a record. IMS Region Controller module DFSRRC00. Check that
Explanation: Internal error. Contact IBM Technical the data server JCL includes the IMS RESLIB in the
Support at www.ibm.com/support. STEPLIB concatenation. Also check the JES output of
the data server for the z/OS abend code associated
with the error.
0x0057006D (5701741) CICS error doing an end
browse.
0x00570075 (5701749) The IMS region controller
Explanation: Internal error. Contact IBM Technical abnormally terminated.
Support at www.ibm.com/support.
Explanation: The IMS region controller abended.
Generally, this is a User Abend code associated with
0x0057006E (5701742) A duplicate key was found in some failure in initializing the IMS Batch environment.
the VSAM PATH when the index was Check the z/OS log and data server log for more
specified as unique. information on the specific abend code. If it is a User
Explanation: You attempted to read, update, or insert Abend code, look up the abend code in the IBM IMS
a record with a duplicate key from/into an index V8 Messages and Codes manual.
defined with the Unique Key attribute. Either redefine
the index so that it is non-unique or remove the 0x00570076 (5701750) The virtual communications
duplicate key record from the file. registration call in the IMS initialization
service failed.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
60 DB2 II System Messages for Classic Federation and Classic Event Publishing
more diagnostic information.
0x00570083 (5701763) The DRA control exit never ran
during DRA initialization.
0x00570093 (5701779) Cannot allocate memory.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Explanation: Not enough available storage in the
message pool. Increase the value for MESSAGE POOL
SIZE in the data server configuration file.
0x00570084 (5701764) The DRA control exit returned
an error return code.
0x00570094 (5701780) Error processing WHERE
Explanation: An unexpected error return code was
clause.
received from the Control Exit in the DRA
environment. See the system log from the data server Explanation: An error occurred while processing the
for more information on the cause. Contact IBM | WHERE clause. Adabas ISN (Internal Sequence
Technical Support at www.ibm.com/support if the | Number) columns are supported on the WHERE
problem persists. | clause, however, only the equality type operators (=,
| IN) are supported. Verify that the WHERE clause is
0x0057008C (5701772) The metadata catalog is
| accurately constructed. Contact IBM Technical Support
at www.ibm.com/support.
incorrect. The table you are referencing
needs to be remapped.
0x00570095 (5701781) Error processing Adabas search
Explanation: A new length-processing algorithm has
command.
been implemented since your table was mapped. Your
mapped length is incompatible with the revised Explanation: An error occurred processing an
algorithm. Remap the table by running the metadata ADABAS find command. See the data server log for
utility with the original grammar. No changes to the more diagnostic information.
grammar are required.
0x00570096 (5701782) Error processing Adabas read
0x0057008D (5701773) The Adabas nucleus is either command.
not active or not accessible.
Explanation: An error occurred processing an
Explanation: An error occurred processing an Adabas ADABAS read command. See the data server log for
command. The response code (148) indicates the more diagnostic information.
database system is not active. See the server log for
more diagnostic information.
0x00570097 (5701783) Cannot locate ADALNK
routine.
0x0057008E (5701774) Error releasing Adabas user
command. Explanation: An error occurred loading the ADALNK
module. This load is executed to assure access to
Explanation: An error occurred processing an Adabas ADABAS. Correct the data server JCL and recycle the
Release Command ID command. See the server log for data server.
more diagnostic information.
0x00570098 (5701784) The Adabas module ADALNK
0x0057008F (5701775) Column data does not fit in the is not reentrant.
query processors supplied buffer.
Explanation: The ADABAS module ADALNK must be
Explanation: Contact IBM Technical Support at re-entrant.
www.ibm.com/support.
0x0057009A (5701786) Error during DATE column
0x00570090 (5701776) Error loading Adabas sub conversion
routine CACADA.
Explanation: An attempt to update/insert a column
Explanation: An error occurred loading the CACADA specified as “USE AS DATE” could not be completed
module. This module is created during the data server because the date format specified was incomplete. The
and Adabas connector installation process. data format must contain month, day, and year in order
to calculate a corresponding ADABAS date value.
Correct the date format in the metadata grammar and
0x00570091 (5701777) Error opening Adabas user
rebuild the table.
session.
Explanation: An error occurred attempting to establish
a session with ADABAS. See the data server log for
0x005700A1 (5701793) Stored procedure memory 0x005700A5 (5701797) Invalid number of parameters
allocation failed. passed to CACTDRA.
Explanation: An attempt to allocate memory failed. Explanation: The number of parameters passed to the
Increase the region size and restart your data server. If CACTDRA is not correct for the type of DL/I call being
the failure cannot be corrected, contact IBM Technical issued. In the data server’s detail log report, the
Support at www.ibm.com/support. You will be asked number of parameters that CACTDRA expected is
for the value in the second word of SQLEXT to assist in displayed as well as the number of parameters
diagnosing the problem. received. The number of parameters is actually one
62 DB2 II System Messages for Classic Federation and Classic Event Publishing
more than passed by the stored procedure. (SAS/C corrected, contact IBM Technical Support at
transient modules add another parameter containing www.ibm.com/support.
the name of the program being invoked.) The
corresponding CACTDRA return code value is 1.
0x005700AB (5701803) No APPC function specified
Operator action: Correct the stored procedure
by user or no APPC definition data
application to supply the correct number of parameters
supplied by user.
for the type of call that is being issued.
Explanation: You are executing a stored procedure
program that is attempting to communicate with a
0x005700A6 (5701798) A PSB is already scheduled.
remote system like IMS or CICS. Three parameters are
Explanation: A stored procedure application issued a required each time you invoke CACSPBR to perform an
SCHD call, but a PSB had already been scheduled by APPC function. One (or more) of those parameters was
the application. Only one PSB can be scheduled by a not specified correctly, as indicated by a zero value in
stored procedure at a time. A CACTDRA TERM call the parameter list. Verify that your program logic
must be issued to unschedule the current PSB prior to includes all three parameters on each invocation of
scheduling a subsequent PSB. The corresponding CACSPBR and that the parameter specifications are
CACTDRA return code value is 10. Operation action: correct. Correct any errors or inconsistencies that are
Correct the application logic. found. Relink your program including CACSPBR and
rerun your stored procedure query.
0x005700A7 (5701799) No PSB has been scheduled.
0x005700AC (5701804) APPC function unknown (not
Explanation: A stored procedure application issued a
OPEN/SEND/RECEIVE/CLOSE).
CACTDRA DL/I call or TERM call without first
successfully scheduling a PSB. The CACTDRA SCHD Explanation: You are executing a stored procedure
call returned an error or the call was never issued. The program that is attempting to communicate with a
corresponding CACTDRA return code value is 11. remote system like IMS or CICS. Three parameters are
Operator action: Correct the application logic. required each time you invoke ‘CACSPBR’ to perform
an APPC function. The first parameter locates a control
block that contains the APPC function to be performed.
0x005700A8 (5701800) Internal error. Invalid
The function specified is not one of the supported
argument data detected by the stored
functions. Correct the requested function to be OPEN,
procedure bridge.
SEND, RECEIVE, or CLOSE. Relink your program
Explanation: This is an internal error. Contact IBM including CACSPBR and rerun your stored procedure
Technical Support at www.ibm.com/support. query.
0x005700A9 (5701801) Internal error. Incorrect buffer 0x005700AD (5701805) Local LU name contains
stamp (SPSTMP1) detected by the stored substitution characters that are
procedure bridge. embedded (for example, not suffix
characters) or the entire local LU name
Explanation: You are executing a stored procedure is suffix characters.
program that is attempting to communicate with a
remote system like IMS or CICS. Buffer contamination Explanation: You are executing a stored procedure
has occurred. Verify that the stored procedure program program that is attempting to communicate with a
being executed is correct. The program you are remote system like IMS or CICS. Three parameters are
executing is identified by the parameter LOADMOD in required each time you invoke CACSPBR to perform an
the stored procedure definition. If the failure cannot be APPC function. The second parameter locates a control
corrected, contact IBM Technical Support at block that contains the APPC control information
www.ibm.com/support. including the Local LU Name. Multiple,
sequentially-numbered, Local LU Names can be
specified by suffixing the Local LU Name with one or
0x005700AA (5701802) Internal error. Incorrect buffer more asterisk (*) characters. An asterisk character
stamp (SPSTMP2) detected by the stored cannot be embedded within the Local LU Name nor
procedure bridge. can the entire Local LU Name be asterisk characters.
Explanation: You are executing a stored procedure Correct the Local LU Name specification. Relink your
program that is attempting to communicate with a program including CACSPBR and rerun your stored
remote system like IMS or CICS. Buffer contamination procedure query.
has occurred. Verify that the stored procedure program
being executed is correct. The program you are
executing is identified by the parameter LOADMOD in
the stored procedure definition. If the failure cannot be
0x005700B1 (5701809) RECEIVE function failed. No 0x005700B4 (5701812) Internal error. Error reported
application return code available. Check when invoking a stored procedure in an
target (remote) system for error or abend LE environment. The data server log
messages. identifies the LE function that failed
and the failing return code.
Explanation: You are executing a stored procedure
program that is attempting to communicate with a Explanation: Internal error. Contact IBM Technical
remote system like IMS or CICS. You have requested an Support at www.ibm.com/support.
APPC RECEIVE be performed. You should have
established the connection previously using the OPEN
0x005700B5 (5701813) Invalid number of parameters
function and you should have sent data to the remote
passed to CACTDCOM.
system using the SEND function. Verify that your
OPEN request and your SEND request were properly Explanation: An invalid number of parameters were
executed. Check for errors or other messages in the passed to CACTDCOM. The number of parameters is
system log or in the job output that may explain the dependent upon which command is being issued. The
RECEIVE failure. Check the system log and job output minimum number of parameters is three and the
for both the local task (data server) and the remote task maximum number is six. This error should occur only
(CICS, IMS, and so on). If the failure cannot be during development of the stored procedure
application program. Correct the parameters used for
64 DB2 II System Messages for Classic Federation and Classic Event Publishing
calling CACTDCOM and rerun your job.
0x005700B9 (5701817) An MVS program load (loadm)
failed. Attempt to load URT ’urtname’
0x005700B6 (5701814) No URT name is available to failed.
CACTDCOM. No ‘(urtname)’ specified
Explanation: The User Requirements Table program
following the ‘_DATACOM’ keyword
could not be loaded. The URT program must be in a
found in the {Work Area | Run
load library that is included in the STEPLIB
Options}. No URT name is available to
concatenation of the data server. Ensure the load
CACTDCOM. No ‘_DATACOM’
module for your URT is in an accessible library and
keyword found in the {Work Area |
rerun your job.
Run Options}.
Explanation: Two variations of this message are
0x005700BA (5701818) URT format is not known.
possible depending upon whether or not the
Partial dump in next log entries.
_DATACOM keyword was supplied. In the first
Research and code changes are required.
variation, the keyword _DATACOM was found in
either the RUN OPTIONS of the cataloged procedure or Explanation: The User Requirements Table program
in a Work Area passed programmatically during the that was loaded does not appear to be a known format.
OPEN processing. However, the expected (urtname) If possible, the first 64 characters and the terminating 8
clause did not immediately follow the keyword or it characters of the URT are dumped, in two separate
did not adhere to the proper syntax. In the second binary displays, to the data server log when the trace
variation, the keyword _DATACOM was not found in level is set to 4 or less. Review the URT content and
either the RUN OPTIONS of the cataloged procedure or determine if it is valid. Changes in the format of User
in a Work Area passed programmatically during the Requirement Tables require code changes in
OPEN processing. CACTDCOM. Format changes are possible when you
migrate to new versions of CA-DATACOM/DB.
This error should occur only during development of
Contact IBM Technical Support at
the stored procedure application program. Correct the
www.ibm.com/support if you believe the CACTDCOM
specification of your URT name used for calling
interface requires code changes.
CACTDCOM and rerun your job.
0x005700BF (5701823) Too many stored procedure 0x005700D6 (5701846) The DB2 CAF module
definition parameters. DSNHLI2 could not be loaded
Explanation: Contact IBM Technical Support at Explanation: The DB2 Universal Database call
www.ibm.com/support. attachment facility module DSNHLI2 could not be
loaded by the data server. Check the data server JCL to
0x005700CF (5701839) A DB2 RRS subsystem insure that the DB2 UDB module DSNALI is in the
SWITCH TO request failed. STEPLIB DD concatenation.
0x005700D0 (5701840) An error occurred in locating Explanation: An attempt to connect to the subsystem
the task identifier during DB2 name specified in the task name field of the SERVICE
initialization. INFO ENTRY for the DB2 CAF thread failed.
Double-check the SERVICE INFO ENTRY for a correct
Explanation: Internal Error. Contact the system DB2 Universal Database subsystem ID in the task name
administrator. field. Also check the data server log for more
information on the failure.
0x005700D1 (5701841) The SERVICE INFO ENTRY
pointer is NULL. 0x005700D8 (5701848) The DB2 CAF service could
not open the DB2 plan.
Explanation: Internal Error. Contact the system
administrator. Explanation: An attempt to OPEN the DB2 Universal
Database plan defined in the SERVICE INFO ENTRY
for the DB2 CAF service failed. Double-check the plan
name specified in the task info field of the SERVICE
INFO ENTRY for the DB2 CAF service. Also check the
data server log for specific error code returned from
66 DB2 II System Messages for Classic Federation and Classic Event Publishing
DB2 Universal Database on the OPEN request.
0x005700E0 (5701856) The virtual communications get
call failed in the DB2 CAF service.
0x005700D9 (5701849) The DB2 CAF service failed to
Explanation: Internal system communication has
close the DB2 plan.
failed. Check the data server log for related messages.
Explanation: An attempt to CLOSE a DB2 Universal If the problem can not be resolved, contact IBM
Database plan resulted in an error code from DB2 UDB. Technical Support at www.ibm.com/support.
Check the data server log for the DB2 UDB error code
returned.
0x005700E1 (5701857) A request for a DB2 CAF
thread failed. Either no DB2 threads are
0x005700DA (5701850) The DB2 CAF service failed to active or all active threads are currently
disconnect from DB2. in use.
Explanation: A disconnect request resulted in an error Explanation: An attempt to acquire a DB2 CAF thread
code from DB2 Universal Database. Check the system has failed. The number of threads allowed is controlled
log for the DB2 UDB error code returned. by the Maximum Task Count (parameter # 5) in the
SERVICE INFO ENTRY for the DB2 CAF service. This
limit may have been reached or there may be a
0x005700DB (5701851) The DB2 CAF service received problem in the DB2 Universal Database subsystem.
an invalid message. Check the data server log for related messages. If the
Explanation: Internal Error. Contact the system problem can not be resolved, contact IBM Technical
administrator. Support at www.ibm.com/support.
0x005700DC (5701852) The DB2 connector session 0x005700E2 (5701858) Unable to obtain the requested
pointer is NULL. storage.
Explanation: Internal error. Contact IBM Technical Explanation: An attempt to allocate memory failed.
Support at www.ibm.com/support. The data server needs more memory. The amount of
memory available for use by the data server is
controlled using the MESSAGE POOL SIZE parameter
0x005700DD (5701853) A request sent to a DB2 CAF in the data server’s Master Configuration Member. See
thread timed out. the MESSAGE POOL SIZE parameter definition in the
Explanation: A statement sent to the DB2 CAF service IBM DB2 Information Integrator Administration Guide and
did not respond within the specified timeout value as Reference for Classic Federation and Classic Event
defined on the CAF SERVICE INFO ENTRY. Check the Publishing for instructions on how to use the MESSAGE
system log and display the data server services for POOL SIZE parameter and how it relates to the total
possible errors. If the problem persists, contact the amount of memory available to the data server. (The
system administrator. total memory available is controlled by the data
server’s REGION size.) If this does not correct the
error, contact IBM Technical Support at
0x005700DE (5701854) A request sent to the DB2 CAF www.ibm.com/support.
service received an invalid response.
Explanation: Internal system communication has 0x005700E3 (5701859) Internal error managing
terminated in an unexpected manner. Check the data previously acquired thread to DB2.
server log for related messages. If the problem can not
be resolved, contact IBM Technical Support at Explanation: Internal error. Contact IBM Technical
www.ibm.com/support. Support at www.ibm.com/support.
0x005700DF (5701855) The virtual communications 0x005700E4 (5701860) SELECT statement (including
put call failed in the DB2 CAF service. WHERE clause) overflows maximum
sized buffer.
Explanation: Internal system communication has
failed. Check the data server log for related messages. Explanation: The area required for the SELECT
If the problem can not be resolved, contact IBM statement including the WHERE clause exceeds the
Technical Support at www.ibm.com/support. maximum allowable buffer. Verify the user supplied
SELECT statement. This could also be caused by
memory corruption. Check the data server log for
related messages. If the problem cannot be resolved,
contact IBM Technical Support at
www.ibm.com/support.
68 DB2 II System Messages for Classic Federation and Classic Event Publishing
IDMS table. See the data server log for the subschema
0x005700F7 (5701879) STORE failed for IDMS record.
name. IDMS subschema names are included in the
See system log from data server for
table mapping grammar. For more information, see the
more information.
utilities descriptions in the IBM DB2 Information
Integrator Administration Guide and Reference for Classic Explanation: The IDMS STORE statement failed while
Federation and Classic Event Publishing. attempting to insert a record. For information on the
subschema name and specific IDMS record code from
the obtain attempt, see the associated error messages in
0x005700F2 (5701874) Bind failed to IDMS record.
the data server log.
See system log from data server for
more information.
0x005700F8 (5701880) ERASE failed for IDMS record.
Explanation: The bind to an IDMS record defined for
See system log from data server for
the table failed. For information on the subschema
more information.
name and specific IDMS record code from the bind
attempt, see the associated error messages in the data Explanation: The IDMS STORE statement failed while
server log. attempting to delete a record. For information on the
subschema name and specific IDMS record code from
the obtain attempt, see the associated error messages in
0x005700F3 (5701875) Ready failed for IDMS area.
the data server log.
See system log from data server for
more information.
0x005700F9 (5701881) COMMIT failed. See system
Explanation: The ready of an IDMS area defined for
log from data server for more
the table failed. For information on the subschema
information.
name and specific IDMS record code from the ready
attempt, see the associated error messages in the data Explanation: The IDMS COMMIT statement failed
server log. while attempting to commit the run-unit update(s) to
the database. For information on the subschema name
and specific IDMS record code from the obtain attempt,
0x005700F4 (5701876) Repositioning (OBTAIN
see the associated error messages in the data server log.
DBKEY) failed for IDMS record. See
system log from data server for more
information. 0x005700FA (5701882) ROLLBACK failed. See system
log from data server for more
Explanation: The IDMS OBTAIN DBKEY statement
information.
failed while attempting to navigate the database. For
information on the subschema name and specific IDMS Explanation: The IDMS ROLLBACK statement failed
record code from the obtain attempt, see the associated while attempting to rollback the run-unit update(s) to
error messages in the data server log. the database. For information on the subschema name
and specific IDMS record code from the obtain attempt,
see the associated error messages in the data server log.
0x005700F5 (5701877) OBTAIN failed for IDMS
record. See system log from data server
for more information. 0x005700FB (5701883) FINISH failed. See system log
from data server for more information.
Explanation: The IDMS OBTAIN statement failed
while attempting to navigate the database. For Explanation: The IDMS FINISH statement failed while
information on the subschema name and specific IDMS attempting to end the run-unit. For information on the
record code from the obtain attempt, see the associated subschema name and specific IDMS record code from
error messages in the data server log. the obtain attempt, see the associated error messages in
the data server log.
0x005700F6 (5701878) MODIFY failed for IDMS
record. See system log from data server 0x005700FC (5701884) CONNECT failed for IDMS
for more information. set. See system log from data server for
more information.
Explanation: The IDMS MODIFY statement failed
while attempting to update a record. For information Explanation: The IDMS CONNECT statement failed
on the subschema name and specific IDMS record code while attempting to establish a record occurrence as a
from the obtain attempt, see the associated error member of a set occurrence. For information on the
messages in the data server log. subschema name and specific IDMS record code from
the obtain attempt, see the associated error messages in
the data server log.
0x00570102 (5701890) The CA-Datacom environment Explanation: The Datacom connector is trying to close
did not initialize correctly. a User Requirements Table. The assigned
CA-DATACOM/DB task area is not available because it
Explanation: An error occurred when attempting to is in use by another user. This may indicate the system
initialize the Datacom environment. See the system log is unusually busy or the other user has failed during
from the data server for more information on the cause processing. If this condition continues to occur, contact
of the error. IBM Technical Support at www.ibm.com/support.
0x00570103 (5701891) Multiple use of a single task 0x00570108 (5701896) Invalid call to open local
area detected. This is an internal error message queue has been detected.
requiring vendor technical support.
Explanation: Internal error. Contact IBM Technical
Explanation: Contact IBM Technical Support at Support at www.ibm.com/support.
www.ibm.com/support.
0x00570109 (5701897) The virtual communications
0x00570104 (5701892) All CA-Datacom task areas are registration call in the CA-Datacom
currently utilized. Retry your request connector failed.
later or increase the number of available
task areas. Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
Explanation: The total number of users allowed to
connect to the Datacom connector is greater than the
number of task areas allocated with 0x0057010A (5701898) Local message queue buffer
CA-DATACOM/DB. Review the SERVICE INFO address is invalid.
ENTRY for the Datacom connector and calculate the Explanation: Internal error. Contact IBM Technical
maximum number of users that can connect to the Support at www.ibm.com/support.
connector by multiplying the maximum number of
tasks times the maximum number of connections per
task. Contrast that number with the number of task 0x0057010B (5701899) Timed out waiting for an open
areas designated for use by the Datacom connector in or close URT command to execute.
field 10 of the SERVICE INFO ENTRY for the Datacom Explanation: Internal error. Contact IBM Technical
Initialization Service. Users requesting service when all Support at www.ibm.com/support.
task areas are busy are rejected by the Datacom
connector. Either increase the number of task areas
allocated with CA-DATACOM/DB or reduce the 0x0057010C (5701900) Invalid local queue message
number of user that can connect to the Datacom received.
connector concurrently. Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x00570105 (5701893) Can’t access allocated task area.
It is locked by another user. 0x0057010D (5701901) The virtual communications
Explanation: The Datacom connector is trying to get call in the CA-Datacom connector
execute a database command. The assigned failed.
CA-DATACOM/DB task area is not available because it Explanation: Internal error. Contact IBM Technical
is in use by another user. This may indicate the system Support at www.ibm.com/support.
is unusually busy or the other user has failed during
processing. Retry your query at a later time. If you are
unable to correct the error, contact IBM Technical
70 DB2 II System Messages for Classic Federation and Classic Event Publishing
0x0057010E (5701902) The virtual communications 0x00570114 (5701908) CA-Datacom database
put call in the CA-Datacom connector processing request failed.
failed.
Explanation: A call to CA-Datacom has returned with
Explanation: Internal error. Contact IBM Technical a zero return code, but the process did not complete
Support at www.ibm.com/support. normally. See the corresponding entry in this document
for the return code.
0x0057010F (5701903) Cannot allocate memory. Check SQLEXT contains 00570114,00FnFnxx where nn is the
log for reason. CA-Datacom return code and xx is the hexadecimal
CA-Datacom internal return code.
Explanation: There is not enough memory to allocate
storage required for the interface calls to If you are unable to correct the error, contact IBM
CA-DATACOM/DB. Stop the data server, increase the Technical Support at www.ibm.com/support.
region size and restart the data server. If you are
unable to correct the error, contact IBM Technical
0x00570115 (5701909) RRS is enabled but the URT
Support at www.ibm.com/support.
supplied is not compatible for RRS
processing.
0x00570110 (5701904) URT specified in the metadata
Explanation: The URT supplied for processing is not
catalog could not be loaded. Check log
Version 10.0 or later. Support for RRS is available only
for system code and reason code from
in Version 10.0 SP02 and later. Assemble your URT
LOAD.
using Version 10.0 or later libraries.
Explanation: An operating system load of the User
SQLEXT contains 00570115,vrmmddyy where vr is the
Requirements Table, specified in the CAC catalog for
URT Version/Release and mmddyy is the URT assembly
the table identified in the current query, has failed.
date.
Ensure that the specified URT is accessible via the
STEPLIB DD concatenation in the data server task. The If you are unable to correct the error, contact IBM
System Code and reason code from the operating Technical Support at www.ibm.com/support.
system load is available in the data server log. If you
are unable to correct the error, contact IBM Technical
Support at www.ibm.com/support.
0x00570121 (5701921) The VSAM environment has 0x00570128 (5701928) The virtual communications get
terminated. call failed in the VSAM connector.
Explanation: The VSAM service is not available Explanation: Internal error. Contact IBM Technical
because it was never started, it was shut down, or is Support at www.ibm.com/support.
being shut down. Verify that the VSAM service is
accessible, and try again.
0x00570129 (5701929) The virtual communications put
call failed in the VSAM connector.
0x00570122 (5701922) The VSAM environment did
Explanation: Internal error. Contact IBM Technical
not initialize correctly.
Support at www.ibm.com/support.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x0057012A (5701930) Unable to obtain the requested
storage.
0x00570123 (5701923) The VSAM environment has
Explanation: Cannot allocate control blocks due to a
been corrupted.
lack of storage. Restart using a larger value for the
Explanation: Internal error. Contact IBM Technical REGION= parameter.
Support at www.ibm.com/support.
0x00570170 (5702000) Fragment not found. 0x00570177 (5702007) Attempting to define a table
with no columns. At least one column
Explanation: Internal error. Contact IBM Technical
must be defined.
Support at www.ibm.com/support.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x00570171 (5702001) INSERT sequence error. An
INSERT for the table definition must be
performed before columns or fragments 0x0x000570178 (5702008) Attempting to define a table
can be inserted. with no fragments. At least one
fragment must be defined.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x00570172 (5702002) Attempting to insert a column
or fragment for a different table name 0x00570179 (5702009) Attempting to define a index
than was identified when the table was with no keys. At least one key must be
inserted. defined.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570173 (5702003) Attempting to insert a key for a 0x0057017A (5702010) The COLNO and
different index name than was COLUMN_SEQUENCE_NUMBER
identified when the index was inserted. definitions for a column are not
consistent.
Explanation: Internal error. Contact IBM Technical
COLUMN_SEQUENCE_NUMBER must
Support at www.ibm.com/support.
be 1 greater than COLNO.
Explanation: Internal error. Contact IBM Technical
0x00570174 (5702004) Attempting to insert a fragment
Support at www.ibm.com/support.
with a fragment identifier that is greater
than the number of fragments identified
in the table definition. 0x0057017C (5702012) Invalid value supplied for
DYNAMIC_ALLOCATION column.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x00570175 (5702005) Attempting to insert a column
with a COLNO that is greater than the 0x0057017D (5702013) Invalid value supplied for
number of columns identified in the FILE_ORGANIZATION column.
table definition.
Explanation: Internal error. Contact IBM Technical
Explanation: Internal error. Contact IBM Technical Support at www.ibm.com/support.
Support at www.ibm.com/support.
0x0057017E (5702014) Invalid value supplied for
0x00570176 (5702006) Attempting to insert a key with SIGNED column.
a COLNO that is greater than the
Explanation: Internal error. Contact IBM Technical
number of keys identified in the index
Support at www.ibm.com/support.
definition.
Explanation: Internal error. Contact IIBM Technical
Support at www.ibm.com/support.
0x00570180 (5702016) Invalid value supplied for 0x0057018A (5702026) Invalid value supplied for
DBNAME column. DBD_TYPE column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570181 (5702017) Invalid value supplied for 0x0057018B (5702027) Invalid value supplied for
DBMS column. FIELD_TYPE column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570182 (5702018) Invalid value supplied for 0x0057018C (5702028) Invalid value supplied for
COLTYPE column. XDFLD_IN_RECORD column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570183 (5702019) Invalid value supplied for 0x0057018D (5702029) Invalid value supplied for IMS
NATIVE_DATA_TYPE column. FIELD_TYPE column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570184 (5702020) Invalid value supplied for 0x0057018E (5702030) Invalid value supplied for
DB2_DATA_TYPE column. IDMS VARIABLE_LENGTH column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570185 (5702021) Invalid value supplied for 0x0057018F (5702031) Invalid value supplied for
NULLABLE column. IDMS ACCESS_METHOD column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570186 (5702022) Invalid value supplied for 0x00570190 (5702032) Invalid value supplied for
FILE_ORGANIZATION column. SET_TYPE column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570187 (5702023) Invalid value supplied for 0x00570191 (5702033) Invalid value supplied for
CLUSTER_TYPE column. TARGET_IS_OWNER column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00570188 (5702024) Invalid value supplied for 0x00570192 (5702034) Invalid value supplied for
UNIQUERULE column. AREA_NAME column.
Explanation: Internal error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
76 DB2 II System Messages for Classic Federation and Classic Event Publishing
0x00570193 (5702035) Invalid value supplied for
CALC_KEY column.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x00600001 (6291457) No SQLDA passed to IMS 0x00600006 (6291462) A duplicate input message
transaction services. The run-time parameter has been defined.
environment has been corrupted.
Explanation: The stored procedure definition contains
Explanation: Internal error. Contact IBM Technical a duplicated input message parameter definition. Refer
Support at www.ibm.com/support. to the stored procedure documentation for the IMS
Transaction Services stored procedure you are
attempting to invoke for a description of the
0x00600002 (6291458) A null parameter has been
parameters that need to be defined.
passed to IMS transaction services.
Explanation: The client application passed a null
0x00600007 (6291463) A duplicate conversation ID
parameter when the IMS Transaction Services stored
input-output parameter has been
procedure was executed. Null parameters are not
defined.
allowed for the IMS Transaction Services stored
procedure you are executing. Refer to the stored Explanation: The stored procedure definition contains
procedure descriptions for information about the a duplicated conversation ID input-output parameter
parameters that need to be defined for the IMS definition. Refer to the stored procedure documentation
Transaction Services stored procedure you are for the IMS Transaction Services stored procedure you
attempting to invoke. are attempting to invoke for a description of the
parameters that need to be defined.
0x00600003 (6291459) An unknown type of parameter
has been passed to IMS transaction 0x00600008 (6291464) A duplicate sync-point action
services. The run-time environment has input parameter has been defined.
been corrupted.
Explanation: The stored procedure definition contains
Explanation: Internal error. Contact IBM Technical a duplicated action input parameter definition. Refer to
Support at www.ibm.com/support. the IMS Transaction Services Commit/Rollback stored
procedure documentation for a description of the
parameters that need to be defined.
0x00600004 (6291460) A duplicate output message
parameter has been defined.
0x00600009 (6291465) A duplicate conversation state
Explanation: The stored procedure definition contains
input parameter has been defined.
a duplicated output message parameter definition.
Refer to the stored procedure documentation for the Explanation: The stored procedure definition contains
IMS Transaction Services stored procedure you are a duplicated conversation state input parameter
attempting to invoke for a description of the definition. Refer to the appropriate interactive mode
parameters that need to be defined. conversational transaction stored procedure
documentation for a description of the parameters that
need to be defined.
0x00600005 (6291461) A duplicate processing status
output parameter has been defined.
0x0060000A (6291466) An invalid output parameter
Explanation: The stored procedure definition contains
has been defined.
a duplicated processing status output parameter
definition. Refer to the stored procedure documentation Explanation: You have defined an output parameter
for the IMS Transaction Services stored procedure you whose signature IMS Transaction Services does not
are attempting to invoke for a description of the recognize. Refer to the stored procedure documentation
parameters that need to be defined. for the IMS Transaction Services stored procedure you
are attempting to invoke for a description of the
parameters that need to be defined.
84 DB2 II System Messages for Classic Federation and Classic Event Publishing
Update the RUN OPTIONS parameter and supply a Services Guide for Classic Federation for the meanings of
valid security flag value. Reload the stored procedure each of these values.
definition in the system catalog and run the client
Correct the client application and run again.
application again.
0x00600021 (6291488) The contents of the action 0x00600025 (6291492) No data received from the IMS
parameter are invalid. transaction.
Explanation: You are attempting to invoke the IMS Explanation: An APPC/MVS receive and wait call
Transaction Services Commit/Rollback stored returned and reported that no data was received from
procedure, but the client application supplied an the IMS transaction, when data was expected.
invalid value for the action input parameter.
This error indicates that the IMS transaction
Valid values are 1and 2. See the IBM DB2 Information encountered a severe error while processing the input
Integrator Transaction Services Guide for Classic Federation message(s), but the IMS transaction did not abnormally
for the meanings of each of these values. terminate. Generally, this error condition occurs when
the IMS input message has not been formatted
Correct the client application and run it again.
properly.
Check the client application to ensure that the
application is creating the IMS input message(s) in the
format that the IMS transaction is inspecting. After
correcting the client application, run again.
86 DB2 II System Messages for Classic Federation and Classic Event Publishing
0x00600026 (6291493) Error reported when attempting 0x0060002d (6291501) Only one input message
to create a result set. parameter has been defined for an
atomic conversational stored procedure
Explanation: An error was reported when IMS
definition. At least two input message
Transaction Services attempted to create a result set.
parameters must be defined.
The return code returned by CACRSCR is also included
with this message. Explanation: Contact IBM Technical Support at
www.ibm.com/support.
If the CACRSCR return code is related to a B-tree error,
then most likely there are problems with the LD TEMP
SPACE parameter. Look up the appropriate error 0x0060002e (6291502) More than ten number of
message to correct the problem. For all other error messages input-output parameters have
codes, contact IBM Technical Support at been defined. The limit is ten.
www.ibm.com/support.
Explanation: Contact IBM Technical Support at
www.ibm.com/support.
0x00600027 (6291494) Error reported inserting a row
in the result set.
Explanation: An error was reported when IMS
Transaction Services attempted to insert a row in the
result set. The return code returned by CACRSIN is
also included with this message.
If the CACRSIN return code is related to a B-tree error,
then most likely there are problems with the LD TEMP
SPACE parameter. Look up the appropriate error
message to correct the problem. Contact IBM Technical
Support at www.ibm.com/support.
0x00630008 (6488072) Task identifier not found. 0x00630011 (6488081) SERVICE INFO ENTRY is
NULL.
Explanation: Internal error. Connection handler has
terminated. Explanation: Internal error. Connection handler has
terminated.
0x00630009 (6488073) Configuration information not
found.
Explanation: Internal error. Connection handler has
terminated.
0x00670001 (6750209) Pointer to service control block 0x00670013 (6750227) Local queue receive failure.
is NULL.
Explanation: Lost session with partner.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x00670014 (6750228) Local queue send failure.
Explanation: Lost session with partner.
0x00670002 (6750210) Pointer to command structure is
NULL.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x0068000A (6815754) Memory allocation failed. 0x00680014 (6815764) Socket accept failure.
Explanation: Increase the Message Pool Size for the Explanation: Internal error. Contact IBM Technical
failing component. z/OS components might also need Support at www.ibm.com/support.
to increase their region size. See the description of the
Message Pool Size parameter the IBM DB2 Information
0x00680015 (6815765) Socket select failure.
Integrator Administration Guide and Reference for Classic
Federation and Classic Event Publishing for more Explanation: Internal error. Contact IBM Technical
information about this and related parameters. Support at www.ibm.com/support.
0x0068000C (6815756) No services available. 0x00680016 (6815766) TCP/IP message larger than
buffer.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x0068000D (6815757) Invalid port number or name.
0x00680017 (6815767) Socket receive failure.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Explanation: Unexpected session outage.
0x0068000E (6815758) Invalid IP address or host 0x00680018 (6815768) Socket send failure.
name.
Explanation: This error indicates that the session was
Explanation: Invalid host name. not available when data was sent. This problem is
typically caused by session outages.
0x0068000F (6815759) Invalid socket. Contact IBM Technical Support at
www.ibm.com/support.
Explanation: IP address could not find port.
98 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 28. Virtual communications interface error messages
(00690001–0069000F)
This section contains the virtual communications interface error messages, which
are in the range 00690001–0069000F (6881281–6881295).
104 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 31. ICU/NLS error messages
(0x006F0001–0x006F000A)
This section contains the ICU/NLS error messages, which are in the range
0x006F0001–0x006F000A (7274497–7274506).
0x006F0001 (7274497) Codepage load error. 0x006F0009 (7274505) Error initializing the ICU
conversion environment.
Explanation: The code page specified may not be
supported by ICU4C. Check the code page Explanation: Error reported when ICU called to
configuration for the data server and the client. The initialize the runtime environment. This is an internal
data source configuration overrides the ODBC error.
Administrator configuration. The ODBC client may not
be installed properly.
0x006F000A (7274506) SQL statement encoding error.
Explanation: Either a wrong code page is being used,
0x006F0002 (7274498) String encoding error.
or the characters in the SQL statement do not have a
Explanation: Either an incorrect code page is being server code page equivalent.
used, or there are characters in the data for which there
are no equivalent characters in the server code page.
0x00800001 (8388609) Missing or invalid remote LU 0x00800021 8388641 Error opening VTAM ACB.
name.
Explanation: VTAM is unable to open the ACB due to
Explanation: Contact IBM Technical Support at a configuration mismatch. Review configuration
www.ibm.com/support. parameters.
0x00800002 (8388610) Missing or invalid local LU 0x00800022 (8388642) VTAM session logon error.
name.
Explanation: Configuration mismatch. Review
Explanation: Contact IBM Technical Support at configuration parameters.
www.ibm.com/support.
0x00800023 (8388643) Invalid local LU name.
0x00800003 (8388611) Missing or invalid mode table
Explanation: Configuration mismatch. Review
information.
configuration parameters.
Explanation: Contact IBM Technical Support at
www.ibm.com/support.
0x00800024 (8388644) Invalid remote LU name.
Explanation: Configuration mismatch. Review
0x00800004 (8388612) Missing or invalid application
configuration parameters.
program name.
Explanation: Contact IBM Technical Support at
0x00800025 (8388645) Invalid log mode.
www.ibm.com/support.
Explanation: Configuration mismatch. Review
configuration parameters.
0x00800005 (8388613) Memory allocation failed.
Explanation: Increase the size of the buffer pool size
0x00800026 (8388646) Error receiving FMH5.
with the MESSAGE POOL SIZE parameter.
Explanation: Configuration error. Review
configuration parameters.
0x00800006 (8388614) Session limit exceeded.
Explanation: Maximum number of sessions has been
0x00800027 (8388647) Invalid TP name.
reached. Increase the maximum number of sessions
(configure). Explanation: Configuration error. Review
configuration parameters.
0x00800007 (8388615) No services available.
0x00800028 (8388648) Error closing the VTAM ACB.
Explanation: Maximum number of services has been
activated. Increase the maximum number of services Explanation: VTAM is unable to close the ACB.
(configure).
0x00800029 (8388649) VTAM send error.
0x00800009 (8388617) Session management error.
Explanation: Internal VTM Error. Contact IBM
Explanation: Internal error. Contact IBM Technical Technical Support at www.ibm.com/support.
Support at www.ibm.com/support.
0x0080002A (8388650) VTAM receive any, GDS
0x0080000A (8388618) Session management variable error.
environment corrupted.
Explanation: Internal VTM Error. Contact IBM
Explanation: Internal error. Contact IBM Technical Technical Support at www.ibm.com/support.
Support at www.ibm.com/support.
110 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 34. VSAM/IAM service messages
(00810000–00810036)
This section contains the VSAM/IAM service messages, which are in the range
00810000–00810036 (8454144–8454198).
0x00810001 (8454145) An error occurred in locating 0x00810007 (8454151) Allocation of the VSAM
the task identifier during VSAM service environment structure failed.
initialization.
Explanation: There is not enough memory to allocate
Explanation: Internal error. Contact IBM Technical control blocks required to manage the environment for
Support at www.ibm.com/support. connections to the VSAM service. Stop the data server,
increase the region size, and restart the data server. If
you are unable to correct the error, contact IBM
0x00810002 (8454146) The SERVICE INFO ENTRY
Technical Support at www.ibm.com/support.
pointer is NULL.
Explanation: Double-check the SERVICE INFO
0x00810008 (8454152) Memory allocation failed.
ENTRY definition for the VSAM service.
Explanation: There is not enough memory to allocate
control blocks required to manage the VSAM datasets.
0x00810003 (8454147) The VSAM service has already
Stop the data server, increase the region size, and
been initialized.
restart the data server. If you are unable to correct the
Explanation: The master configuration file contains a error, contact IBM Technical Support at
SERVICE INFO ENTRY for more than one VSAM www.ibm.com/support.
service. The first SERVICE INFO ENTRY is processed
and all subsequent definitions are failed with this error
0x00810009 (8454153) Invalid local queue message
message. Remove or comment out any extra SERVICE
received by VSAM service.
INFO ENTRY definitions to clear up this message.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support.
0x00810004 (8454148) The virtual communications
registration call in the VSAM service
failed. 0x00810021 (8454177) The VSAM file system
encountered a dynamic allocation error.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Explanation: A Dynamic allocation error has occurred.
The System Code and DYNALLOC reason code is
available in the data server log.
0x00810005 (8454149) The virtual communication
open call in the VSAM service failed.
0x00810022 (8454178) The VSAM file system
Explanation: Internal error. Contact IBM Technical
encountered an open error.
Support at www.ibm.com/support.
Explanation: An Open error has occurred. The return
code and dataset name is available in the data server
0x00810006 (8454150) The message allocation call for
log.
the VSAM service message buffer
failed.
0x00810023 (8454179) The VSAM file system
Explanation: There is not enough memory to allocate
encountered a close error.
a message buffer for communication with the data
server’s region controller. Stop the data server, increase Explanation: A Close error has occurred. The return
the region size, and restart the data server. If you are code and dataset name is available in the data server
unable to correct the error, contact IBM Technical log.
Support at www.ibm.com/support.
112 DB2 II System Messages for Classic Federation and Classic Event Publishing
the required associations could not be found. Ensure
that the IAM file is properly defined and the alternate
index is set up correctly.
0x00850003 (8716291) Cross memory session control 0x0085000C (8716300) Cross memory receive error.
block not found on put operation.
Explanation: Contact IBM Technical Support at
Explanation: Contact IBM Technical Support at www.ibm.com/support.
www.ibm.com/support.
0x00851001 (8720385) Unable to locate cross memory
0x00850009 (8716297) No resources available. queue token.
Explanation: Cannot allocate control blocks due to a Explanation: Name/token services failure. IPL is
lack of storage. Restart using larger REGION= required.
parameter.
0x00851002 (8720386) Cross memory server address
0x0085007 (8716295) Session limit exceeded. space no longer active.
Explanation: Maximum number of sessions has been Explanation: No active queue name listening. Verify
reached. Increase maximum number of sessions that the queue name is correct in the client
(configure). configuration file, and verify that the data server has
been started.
0x0085008 (8716296) No services available.
0x00851004 (8720388) Invalid cross memory queue
Explanation: Maximum number of services has been
name.
activated. Increase maximum number of services
(configure). Explanation: Invalid three-part name. See the
configuration documentation.
0x008500B (8716297) Cross memory message received
that is larger than the allocated buffer. 0x00851005 (8720389) Unable to retrieve cross
memory global name/token.
Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Explanation: Name/token services failure. IPL is
required.
0x0085000E (8716302) Cross memory session error.
0x00851006 (8720390) Unable to locate cross memory
Explanation: Contact IBM Technical Support at
queue entry.
www.ibm.com/support.
Explanation: Maximum number of available system
LX entries has been reached. IPL is required.
0x0085000D (8716301) Invalid cross memory session
number received.
0x00851008 (8720392) Error allocating cross memory
Explanation: Contact IBM Technical Support at
queue entry storage.
www.ibm.com/support.
Explanation: CSA is out of space. IPL is required.
0x0085000A (8716298) Memory allocation failed.
0x00851009 (8720393) Error inserting cross memory
Explanation: Increase MESSAGE POOLSIZE
queue entry.
parameter.
Explanation: Unable to insert LX entry. Contact IBM
Technical Support at www.ibm.com/support.
0x00850012 (8716306) XM Accept error.
Explanation: Cannot accept an incoming session.
Either there is a control block error, or the maximum
number of sessions has been reached.
0x0085100B (8720395) Error allocating cross memory 0x00853002 (8728578) Cross memory unable to locate
management structure. correlation service.
Explanation: Contact IBM Technical Support at Explanation: The data server has terminated. Restart
www.ibm.com/support. server. If problem reoccurs, contact IBM Technical
Support at www.ibm.com/support.
0x0085100C (8720396) Error creating cross memory
data space. 0x00853003 (8728579) Cross memory unable to locate
management structure.
Explanation: Unable to allocate data space. Contact
IBM Technical Support at www.ibm.com/support. Explanation: The data server has terminated. Restart
server. If problem reoccurs, contact IBM Technical
Support at www.ibm.com/support.
0x0085100D (8720397) Error establishing cross
memory data space access.
0x00854001 (8732673) No data spaces available for use
Explanation: Data space is not accessible. Contact IBM
by cross memory.
Technical Support at www.ibm.com/support.
Explanation: Data space is out of available storage.
Contact IBM Technical Support at
0x0085100E (8720398) Error creating local cross
www.ibm.com/support.
memory name/token.
Explanation: Name/token services failure. Contact
0x00854002 (8732674) Cross memory unable to locate
IBM Technical Support at www.ibm.com/support.
management control block.
Explanation: Control block failure. Contact IBM
0x0085100F (8720399) Error releasing cross memory
Technical Support at www.ibm.com/support.
queue entry.
Explanation: The attempt to free the CSA area failed.
0x00854003 (8732675) Invalid cross memory
Contact IBM Technical Support at
management control block identifier.
www.ibm.com/support.
Explanation: Invalid control block. Contact IBM
Technical Support at www.ibm.com/support.
0x00851010 (8720400) Error deleting cross memory
data space.
0x00855000 (8736768) Cross memory session limit
Explanation: Unable to delete data space. Contact IBM
exceeded.
Technical Support at www.ibm.com/support.
Explanation: Contact IBM Technical Support at
www.ibm.com/support.
0x00851011 (8720401) Error removing cross memory
data space access.
0x00855001 (8736769) Cross memory management
Explanation: Control block linkage failure. Contact
control block corrupted.
IBM Technical Support at www.ibm.com/support.
Explanation: Invalid control block. Contact IBM
Technical Support at www.ibm.com/support.
0x00851012 (8720402) Error deleting cross memory
local name/token.
0x00855002 (8736770) Cross memory server not found.
Explanation: Name/token services failure. Contact
IBM Technical Support at www.ibm.com/support. Explanation: Invalid control block. Contact IBM
Technical Support at www.ibm.com/support.
116 DB2 II System Messages for Classic Federation and Classic Event Publishing
0x00855003 (8736771) Cross memory queue name 0x00859001 (8753153) Cross memory data space
already in use. corrupted.
Explanation: Attempt to start duplicate service. Check Explanation: Storage overlay. Contact IBM Technical
the data source name on start. Support at www.ibm.com/support.
0x00855005 (8736773) Invalid cross memory 0x00859002 (8753154) Cross memory data space not
management control block address. initialized.
Explanation: Internal XM error. Contact IBM Technical Explanation: Data space initialization error. Contact
Support at www.ibm.com/support. IBM Technical Support at www.ibm.com/support.
0x00857001 (8744961) Cross memory session not 0x00859003 (8753155) Cross memory data space
found. corrupted.
Explanation: Session already terminated. Check Explanation: Internal error. Contact IBM Technical
session log. Support at www.ibm.com/support.
0x00857003 (8744963) Invalid cross memory slot 0x00859004 (8753156) Cross memory data space
number on input. corrupted.
Explanation: Internal XM error. Contact IBM Technical Explanation: Internal error. Contact IBM Technical
Support at www.ibm.com/support. Support at www.ibm.com/support.
0x00880021 (8912897) Error getting ALET access to the 0x00880027 (8912904) Invalid EXTEND subparameter
hiperspace
Explanation: The EXTEND subparameter of the LD
Explanation: Internal program error. Contact IBM TEMP SPACE parameter is invalid. Valid settings are
Technical Support at www.ibm.com/support. xM and xG, where x is the initial number of megabytes
(M) or gigabytes (G) of space you want to extend the
storage area by at a time. Verify that the entry uses M
0x00880022 (8912899) Error getting page boundary
or G to specify the unit, that the number of units is
storage
valid in your environment, and that the number of
Explanation: There was an error in the MVS™ units does not exceed the MAX subparameter.
STORAGE OBTAIN macro. Retrieve the
Data(xxxxxxxx,yyyyyyyy) portion of the message log.
0x00880028 (8912905) Error releasing page boundary
Look for the xxxxxxxx value in IBM’s IBM z/OS MVS
storage
Programming: Authorized Assembler Services Reference for
information on how to resolve the issue. Explanation: Internal program error. Contact IBM
Technical Support at www.ibm.com/support.
0x00880023 (8912900) Invalid HIPERSPACE
parameter 0x00880029 (8912906) Error releasing ALET access to
the hiperspace
Explanation: The first entry of the LD TEMP SPACE
parameter may be misspelled. Check to make sure that Explanation: Internal program error. Contact IBM
it is spelled HIPERSPACE. If it is, contact IBM Technical Support at www.ibm.com/support.
Technical Support at www.ibm.com/support.
0x0088002A (8912938) Error deleting the hiperspace
0x00880024 (8912901) Invalid HIPERSPACE
Explanation: Internal program error. Contact IBM
subparameter
Technical Support at www.ibm.com/support.
Explanation: One of the subparameters of the LD
TEMP SPACE parameter is misspelled. Valid spellings
0x0088002B (8912939) Error reading from the
for the subparameters in this parameter are INIT, MAX,
hiperspace
and EXTEND.
Explanation: Internal program error. Contact IBM
Technical Support at www.ibm.com/support.
0x00880025 (8912902) Invalid MAX subparameter
Explanation: The MAX subparameter of the LD TEMP
0x0088002C (8912940) Error trying to read past end of
SPACE parameter is invalid. Valid settings are xM and
capacity
xG, where x is the maximum number of megabytes (M)
or gigabytes (G) of space you want to allocate. Verify Explanation: Internal program error. Contact IBM
that the entry uses M or G to specify the unit, and that Technical Support at www.ibm.com/support.
the number of units is valid in your environment.
0x0088002D (8912941) Error writing to the hiperspace
0x00880026 (8912903) Invalid INIT subparameter
Explanation: Internal program error. Contact IBM
Explanation: The INIT subparameter of the LD TEMP Technical Support at www.ibm.com/support.
SPACE parameter is invalid. Valid settings are xM and
xG, where x is the initial number of megabytes (M) or
gigabytes (G) of space you want to allocate. Verify that
120 DB2 II System Messages for Classic Federation and Classic Event Publishing
Chapter 37. Enterprise server error messages
(0x00880002–0x0088001C)
This section contains the enterprise server error messages, which are in the range
0x00880002–0x0088001C (8912898–8912924).
0x00880002 (8912898) No task data specified on 0x0088001A (8912922) Error connecting to target data
enterprise server SERVICE INFO server.
ENTRY definition.
Explanation: Contact IBM Technical Support at
Explanation: Configuration error. www.ibm.com/support.
0x00880003 (8912899) No task data specified on 0x0088001C (8912924) User not found.
enterprise server SERVICE INFO
Explanation: Contact IBM Technical Support at
ENTRY definition.
www.ibm.com/support.
Explanation: Configuration error.
126 DB2 II System Messages for Classic Federation and Classic Event Publishing
-153 A CREATE VIEW statement did not -183 An arithmetic operation on a DATE or
have a column name list TIMESTAMP value produced a value
that is out of the range of valid dates
Explanation: A CREATE VIEW statement contained
select list expressions which were unnamed. When a Explanation: The calculation of a DATE or
CREATE VIEW includes unnamed select list items, the TIMESTAMP value resulted in a date that is outside the
normally optional column name list for the view is range of 0001-01-01 and 9999-12-31. Correct the SQL
required so all items in the select list have a name. statement.
Correct the SQL statement. In this case, you can either
provide names for all columns in the view or name the -185 LOCAL date and time format not
unnamed expressions in the select list with the AS supported
specification.
Explanation: The CHAR scalar function was specified
for a date or time with the LOCAL formatting option.
-156 The target of a MAP INDEX statement the LOCAL option is not supported. Correct the SQL
is not a table statement.
Explanation: A MAP INDEX statement references a
catalog item that is not a table. Correct the SQL -203 A reference to a column name is
statement. ambiguous
Explanation: An unqualified column name in the
-158 Invalid column list for view query is ambiguous. The named column exists in more
than one table in the query and must be qualified with
Explanation: The number of named columns in a
either a correlation name or a combination owner and
CREATE VIEW statement does not match the number
table name to resolve the ambiguity.
of select items in the select statement for the view.
Correct the SQL statement. Correct the SQL statement. If the cause of the error is
not apparent by sight-checking the SQL, consult the
data server log for the column name in error.
-170 Invalid number of arguments
Explanation: The number of named columns in a
-204 A table, view, or procedure name was
create view statement does not match the number of
not found
select items in the select statement for the view. Correct
the SQL statement. Explanation: A table, view, or procedure name passed
in an SQL statement was not found in the system
catalog.
-171 Invalid function argument
Correct the SQL statement. If the cause of the error is
Explanation: The data type, length, or value of a
not apparent by sight-checking the SQL, consult the
function argument is invalid. Correct the SQL
data server log for the name in error.
statement. If the cause of the error is not apparent by
sight-checking the SQL, consult the data server log for
more information. -206 A column name was not found
Explanation: A column name in the SQL statement
-181 The string representation of a was not found in any of the tables or views included in
DATETIME value is not valid the statement.
Explanation: A String form of a DATE, TIME, or Correct the SQL statement. If the cause of the error is
TIMESTAMP value could not be converted to an not apparent by sight-checking the SQL, consult the
internal date or time format because it either contained data server log for the column name in error.
invalid characters or was not in a recognized date,
time, or timestamp format. Correct the SQL statement.
-208 An invalid column was included in the
ORDER BY clause
-182 An arithmetic expression with a
Explanation: A column name in the ORDER BY clause
DATETIME value is invalid
is invalid because it was not included in the select list
Explanation: Arithmetic expressions with datetime of the SELECT statement. Correct the SQL statement.
values or labeled durations are invalid. Correct the SQL
statement.
128 DB2 II System Messages for Classic Federation and Classic Event Publishing
-408 An UPDATE or INSERT value is not -421 The operands of a UNION do not have
compatible with the data type of the the same number of result columns
target column
Explanation: The number of result columns in a
Explanation: An attempt was made to INSERT or UNION select list did not match the number of result
UPDATE a column with a value which is not columns in one of the other UNION select lists. Each
compatible with the data type of the target column. select list in a UNION must have exactly the same
Correct the SQL statement. number of result columns. Correct the SQL statement.
-412 The SELECT CLAUSE of a subquery -469 The stored procedure definition
specifies multiple columns includes one or more OUTPUT
parameters for which no host variable
Explanation: A subselect used in a comparison
was passed
operation specified more than one column. Subselects
used for comparison operations must specify one and Explanation: The CALL statement did not include a
only one result column. host variable for one of the stored procedure OUTPUT
or OUTIN parameters. Every output parameter in a
Correct the SQL statement.
stored procedure definition must have a host variable
passed in its associated CALL statement. Correct the
-415 The corresponding columns UNION do application program.
not have compatible data types
Explanation: The corresponding columns in each table -501 The cursor identified in a FETCH or
of a UNION must have compatible data types based on CLOSE statement is not open.
the position of each column in the UNION select list.
Explanation: The application program attempted to
For example, the first item in each select list in a
either:
UNION must be compatible with the first item in every
table in the UNION. v FETCH using a cursor, or
v CLOSE a cursor
Correct the SQL statement. If the incompatible column
is not apparent by sight-checking the SQL, consult the
at a time when the specified cursor was not open.
data server log for more information on the column
which resulted in this error.
Correct the logic of the application program to ensure
that the cursor is open at the time the FETCH or
-416 An operand of a UNION contained a CLOSE statement is executed.
long SQL column
Explanation: One of the select items in a query -502 The cursor identified in an OPEN
contained a long SQL data type (LONG VARCHAR, statement is already open.
LONG_VARGRAPHIC). Long SQL data types are not
allowed in UNION queries. Explanation: The application program attempted to
execute an OPEN statement for a cursor that was
Correct the SQL statement. already open.
The statement cannot be executed. The cursor was
-419 Invalid decimal divide operation unchanged (not reopened). Correct the logic of the
application program to ensure that it does not attempt
Explanation: A decimal divide operation is invalid
to execute an OPEN statement for a cursor that is
because the algorithm used to determine the decimal
already open.
result calculated a negative scale value.
Correct the SQL statement.
-504 The cursor name is not defined.
Explanation: Cursor was not declared in the
-420 Invalid decimal string
application program before it was referenced.
Explanation: A string representation of decimal data
The statement cannot be executed. Check the
contained invalid characters and could not be
application program for completeness and for a
converted to a decimal data type. Correct the SQL
possible spelling error in the cursor declaration. The
statement.
declaration for a cursor must appear in an application
program before statements that reference the cursor. For
information about cursor-name, see the SQL log.
130 DB2 II System Messages for Classic Federation and Classic Event Publishing
field in any decimal operation is too short to contain
-638 TABLE table-name cannot be created
the result.
because column definition is missing.
A divide exception can occur on a division operation
Explanation: The CREATE TABLE statement does not
on any numeric field type (DECIMAL, FLOAT,
contain any column definition.
SMALLINTI, or INTEGER) by zero, or on a decimal
The SQL statement cannot be executed. Add column division operation when the quotient exceeds the
definition to the statement. specified data-field size.
An exponent overflow can occur when the result
-680 Too many columns specified for a table characteristic of any floating point operation exceeds
127 and the result fraction is not zero.
Explanation: The maximum number of columns
permitted per table is 750. The statement cannot be The statement cannot be executed. In the case of an
executed. Do not attempt to CREATE or ALTER a table INSERT or UPDATE statement, no data is updated or
to contain more than 750 columns. Create separate deleted. If the statement was a cursor controlled
tables as required to hold the additional information. FETCH then the cursor will remain open. If the cursor
was controlled OPEN then the cursor will remain
closed.
-681 Field Procedure encode or decode error
Explanation: An error occurred in encoding or
-802 (continued)
decoding a column within a field procedure. Check for
the following possible errors: Explanation: Examine the SQL statement to see if the
v Invalid value on encode or decode or invalid column cause (or the likely cause) of the problem can be
data type. determined. The problem may be data-dependent, in
which case it will be necessary to examine the data that
v Field procedure function error.
was being processed at the time the error occurred. See
the data server log for information about data types.
The field procedure return code and error message is
written to the server log. Check the log for more
information. -803 Cannot INSERT or UPDATE duplicate
values in an index column.
-682 Cannot load Field Procedure Explanation: An INSERT or UPDATE cannot be
completed due to duplicate values in an index column.
Explanation: The field procedure module cannot be Verify the unique column table constraint definition,
loaded. and that duplicate values will not occur.
The statement cannot be executed. View the server log
output for possible problem information. Ensure that -804 An error was found in the input
the named field procedure is in the STEPLIB DD SQLDA
concatenation or LIBDEF PHASE search chain for the
data server. Explanation: An error occurred in processing the
input SQLDA in a request from the application
program. Contact IBM Technical Support at
-802 Data exception error. www.ibm.com/support.
Explanation: The processing of an SQL arithmetic
function or arithmetic expression that was either in the -811 The results of a subselect produced
SELECT list of an SQL select statement, in the search more than one row
condition of a SELECT, UPDATE, or DELETE statement
during the evaluation of a column function, or in the Explanation: An imbedded subselect produced a
SET clause of the UPDATE statement has encountered result set which contained more than one row of data.
an exception error. Possible reasons are FIXED POINT The subselect as written is restricted to a single row of
OVERFLOW, DECIMAL OVERFLOW, DIVIDE data. Correct the SQL statement.
EXCEPTION, or EXPONENT OVERFLOW. The
possible operations include ADDITION,
-817 Update prohibited (two-phase commit
SUBTRACTION, MULTIPLICATION, DIVISION, and
situation OR Catalog update statement
NEGATION.
(DDL) issued while a connector
A fixed-point overflow can occur during any arithmetic transaction was incomplete)
operation on either INTEGER or SMALLINT fields.
Explanation: A prohibited update statement was
A decimal overflow exception can occur when one or issued while a transaction was in progress for a
more nonzero digits are lost because the destination connector. The update is prohibited for one of the
following reasons:
132 DB2 II System Messages for Classic Federation and Classic Event Publishing
-4904 Unsupported expression -4910 An error occurred during a connector
update requiring a Backout of the
Explanation: An unsupported SQL function or
current transaction. The transaction was
expression was passed to the Query Processor. One of
backed out. See the data server log for
the following unsupported expressions was passed:
specifics of the initial error requiring
v A date or time duration. the transaction backout.
v A date or time scalar function.
Explanation: An error occurred in update processing
v The VARGRAPHIC scalar function. that required backing out the current transaction to
v An unsupported special register. rollback partial updates made to a connector. All
changes made by previous successful updates within
Correct the SQL statement. the transaction were rolled back.
Review the data server log to determine the initial error
-4905 Internal processing error detected that resulted in the -4910 error and transaction
rollback. Correct the SQL as necessary.
Explanation: An unexpected processing error occurred
in the query processor. Contact IBM Technical Support
at www.ibm.com/support.
136 DB2 II System Messages for Classic Federation and Classic Event Publishing
code. Consult the appropriate DB2 UDB documentation
-9999 INTERNAL ERROR; REASON CODE
to interpret the return code and reason code returned
‘n’. CONTACT IBM CORPORATION
by the failing open. Make necessary corrections, and
TECHNICAL SUPPORT.
retry the DB2 import utility.
Explanation: An internal error has occurred. When
you contact IBM Technical Support at
-9999 REQUIRED SYSTEM TABLES NOT
www.ibm.com/support, supply the reason code that
AVAILABLE FOR description
displayed in the message.
PROCESSING.
Explanation: Some required system tables are not
-9999 LOAD FOR PROGRAM name FAILED.
available for the type of processing described.
Explanation: Program load failed so the required description can be replaced by:
entry point could not be located. name can be replaced v IMPORT DB2 TABLE/VIEW: an IMPORT DB2
by: TABLE/VIEW statement has been processed but the
v DSNALI: Call Attachment Facility language interface DB2 Universal Database catalog system tables to
module. Entry point DSNALI handles explicit DB2 support this type of processing do not exist. See
Universal Database connection service requests. warning message related to most recent CONNECT
v DSNHLI2: Call Attachment Facility language TO DB2 statement.
interface module. Entry point DSNHLI2 handles SQL v IMPORT DB2 INDEX: an IMPORT DB2 INDEX
calls. statement has been processed but the DB2 Universal
Database catalog system tables to support this type
Ensure the DB2 Universal Database load module of processing do not exist. See warning message
DSNALI exists and is accessible for loading by the DB2 related to most recent CONNECT TO DB2 statement.
import utility. Retry the DB2 import utility. v ACCESS CATALOG PREFIX ’prefix’: in the currently
connected DB2 Universal Database subsystem, the
-9999 MEMORY ALLOCATION FOR AN area catalog does not contain prefix.SYSTABLES,
FAILED. prefix.SYSCOLUMNS, prefix SYSINDEXES or
prefix.SYSKEYS. No DB2 Universal Database import
Explanation: Could not get storage for the specified processing can be executed. Verify the catalog prefix.
area. area can be replaced by: Verify the DB2 Universal Database subsystem.
v SQLCA,
v SQLDA, Determine why the required tables are not accessible in
the DB2 Universal Database subsystem using the
v SQLDA1, specified prefix. Make necessary corrections, and retry
v SQL STATEMENT BUFFER, the DB2 import utility.
v INDEX ENTRY, or
v INDEX KEY COLUMN. -9999 RESTRICTED SYSTEM TABLE
CANNOT BE CREATED.
Increase the amount of memory available to the
Explanation: SYSTABLES, SYSCOLUMNS,
program and retry the DB2 import utility.
SYSINDEXES, SYSKEYS or SYSTABAUTH has been
specified in an IMPORT as the name of a table to be
-9999 NOT CONNECTED TO DB2 stored in the metadata catalog.
SUBSYSTEM. IMPORT CANNOT
Correct the grammar and retry the DB2 import utility.
CONTINUE.
Explanation: An IMPORT process requires a
-9999 TABLE ASSOCIATED WITH THE
connection to DB2 Universal Database. No connection
INDEX IS NOT A DB2 OBJECT. INDEX
exists at this time. Determine why no connection exists.
IMPORT CANCELED.
Include a CONNECT TO DB2 statement in the
grammar before the IMPORT statement. Make Explanation: The table associated with the index being
necessary corrections, and retry the DB2 import utility. imported was not imported by the DB2 import utility.
If specified, verify the DEFINED ON TABLE creator
-9999 ‘OPEN DB2 PLAN’ FAILED; SSN=‘ssid’, name and table name. If not specified, verify the table
PLAN=‘name’, RC=rc, RSN=x ‘reasoncode’. was not renamed during previous import. Make
necessary corrections, and retry the DB2 import utility.
Explanation: An attempt to open a DB2 Universal
Database plan failed. ssid identifies the DB2 UDB
subsystem. name identifies the plan name. rc is the DB2
UDB return code. reasoncode is the DB2 UDB reason
138 DB2 II System Messages for Classic Federation and Classic Event Publishing
-9999 NO USERID SUPPLIED. CANNOT -9999 ’GETENTIT’ DID NOT RETURN
ACCESS DATA DICTIONARY. ’TABLE’ OCCURRENCE. PATH IS
TABLE-AREA-DATABASE. CHECK
Explanation: The file specified in the DDIDENT DD
DATABASE STRUCTURE. CORRECT
statement does not contain a ’USER =’ parameter.
PROBLEM AND RETRY.
Correct the identification parameters in the DDIDENT
file, and retry the metadata utility. Explanation: The Data Dictionary Service Facility
command GETENTIT did not return the expected
TABLE occurrence. Verify that the ENTITY-
-9999 NO PASSWORD SUPPLIED. CAN NOT
OCCURRENCE-NAME (table name) specified in the
ACCESS DATA DICTIONARY.
grammar. Verify that the correct CA-Datacom System
Explanation: The file specified in the DDIDENT DD Resource Table (DDSRTLM) is being accessed. If you
statement does not contain a ’PASSWORD =’ cannot resolve this error, contact IBM Technical Support
parameter. Correct the identification parameters in the at www.ibm.com/support.
DDIDENT file, and retry the metadata utility.
-9999 ’GETPATH’ (RETURN 1ST
-9999 DSF INITIALIZATION FAILED. OCCURRENCE) FAILED.
CA-DATACOM/DB REQUEST AREA CA-DATACOM/DB REQUEST AREA
RETURN CODE INFORMATION RETURN CODE INFORMATION
’returncode’. ’returncode’.
Explanation: A Data Dictionary Service Facility Explanation: The Data Dictionary Service Facility
initialization command (SYSINITI or USRINITI) has command GETPATH has failed. See the CA-Datacom
failed. See the CA-Datacom documentation for an documentation for an explanation of possible return
explanation of return codes that are possible for each of codes for this command. If your technical personnel
these commands. cannot resolve this error, contact IBM Technical Support
at www.ibm.com/support.
-9999 ’DEFPATH’ FOR TABLE-AREA-
DATABASE FAILED. -9999 WARNING: COLUMN NAME
CA-DATACOM/DB REQUEST AREA ‘column-name’ IS A DB2 RESERVED
RETURN CODE INFORMATION WORD. ENCLOSE WITH " IN SQL
’returncode’. STATEMENT
Explanation: The Data Dictionary Service Facility Explanation: The column-name identified in this
command DEFPATH has failed. See the CA-Datacom message is a reserved word. To use this column name
documentation for an explanation of possible return in an SQL statement, enclose it in quotation marks (")
codes for this command. If your technical personnel not apostrophes (’). Checking for reserved word
cannot resolve this error, contact IBM Technical Support column names and issuing this warning message,
at www.ibm.com/support. where appropriate, is done in both USE TABLE and
USE INDEX processing.
-9999 UNABLE TO ALLOCATE STORAGE.
CORRECT PROBLEM AND RETRY. -9999 UNABLE TO LOAD MODULE
modulename.
Explanation: Could not allocate storage. Increase the
amount of memory available to the program, and retry Explanation: An error occurred loading the module
the metadata utility. named modulename. Ensure the STEPLIB concatenation
includes a library that contains the named module.
-9999 ’GETENTIT’ (ANCHOR ON AN
ENTITY) FAILED. CA-DATACOM/DB -9999 THE ADABAS FIELD NAME fieldname
REQUEST AREA RETURN CODE IS INVALID.
INFORMATION ’returncode’.
Explanation: The Adabas field named fieldname found
Explanation: The Data Dictionary Service Facility in the metadata catalog could not be matched to any
command GETENTIT has failed. See the CA-Datacom field in the Field Definition Table (FDT). Ensure that
documentation for an explanation of possible return the FDT has not changed since the grammar was
codes for this command. If your technical personnel generated and the table was mapped.
cannot resolve this error, contact IBM Technical Support
at www.ibm.com/support.
140 DB2 II System Messages for Classic Federation and Classic Event Publishing
documentation for an explanation of possible return
-9999 LOADING THE ’DDCALL’ INTERFACE
codes for this command. If your technical personnel
FAILED. CHECK THE SYSTEM LOG
cannot resolve this error, contact IBM Technical Support
FOR MESSAGES. CORRECT THE
at www.ibm.com/support.
PROBLEM AND RETRY.
Explanation: The CA-Datacom DDCALL interface
-9999 ’GETMORE’ DID NOT RETURN
program load has failed. The program (CACDCDDC)
’DATABASE’ OCCURRENCE. PATH IS
could not be loaded. Check the system log for
TABLE-AREA-DATABASE. CHECK
messages. Verify that the load module is accessible via
DATABASE STRUCTURE. CORRECT
the STEPLIB DD statement. If you cannot resolve this
PROBLEM AND RETRY.
error, contact IBM Technical Support at
Explanation: The Data Dictionary Service Facility www.ibm.com/support.
command GETMORE did not return the expected
DATABASE occurrence. Verify that the
-9999 ’DEFPATH’ FOR TABLE-ELEMENT
ENTITY-OCCURRENCE-NAME (table name) specified
FAILED. CA-DATACOM/DB REQUEST
in the grammar. Verify that the correct CA-Datacom
AREA RETURN CODE INFORMATION
System Resource Table (DDSRTLM) is being accessed. If
’returncode’.
your technical personnel cannot resolve this error,
contact IBM Technical Support at Explanation: The Data Dictionary Service Facility
www.ibm.com/support. command DEFPATH has failed. See the CA-Datacom
documentation for an explanation of possible return
codes for this command. If your technical personnel
-9999 ’GETMORE’ RETURNED TWO
cannot resolve this error, contact IBM Technical Support
’DATABASE’ OCCURRENCES. PATH IS
at www.ibm.com/support.
TABLE-AREA-DATABASE. CHECK
DATABASE STRUCTURE. CORRECT
PROBLEM AND RETRY. -9999 ’GETENTIT’ DID NOT RETURN
’TABLE’ OCCURRENCE. PATH IS
Explanation: The Data Dictionary Service Facility
TABLE-ELEMENT. CHECK DATABASE
command GETMORE returned an unexpected
STRUCTURE. CORRECT PROBLEM
DATABASE occurrence. Verify that the
AND RETRY.
ENTITY-OCCURRENCE-NAME (table name) specified
in the grammar. Verify that the correct CA-Datacom Explanation: The Data Dictionary Service Facility
System Resource Table (DDSRTLM) is being accessed. If command GETENTIT did not return the expected
your technical personnel cannot resolve this error, TABLE occurrence. If you cannot resolve this error,
contact IBM Technical Support at contact IBM Technical Support at
www.ibm.com/support. www.ibm.com/support.
-9999 ’DEFPATH’ FOR TABLE-FIELD FAILED. -9999 ’DEFPATH’ FOR TABLE-KEY FAILED.
CA-DATACOM/DB REQUEST AREA CA-DATACOM/DB REQUEST AREA
RETURN CODE INFORMATION RETURN CODE INFORMATION
’returncode’. ’returncode’.
Explanation: The Data Dictionary Service Facility Explanation: The Data Dictionary Service Facility
command DEFPATH has failed. See the CA-Datacom command DEFPATH has failed. See the CA-Datacom
documentation for an explanation of possible return documentation for an explanation of possible return
codes for this command. If you cannot resolve this codes for this command. If your technical personnel
error, contact IBM Technical Support at cannot resolve this error, contact IBM Technical Support
www.ibm.com/support. at www.ibm.com/support.
-9999 ’GETENTIT’ DID NOT RETURN -9999 ’GETENTIT’ DID NOT RETURN
’TABLE’ OCCURRENCE. PATH IS ’TABLE’ OCCURRENCE. PATH IS
TABLE-FIELD. CHECK DATABASE TABLE-KEY. CHECK DATABASE
STRUCTURE. CORRECT PROBLEM STRUCTURE. CORRECT PROBLEM
AND RETRY. AND RETRY.
Explanation: The Data Dictionary Service Facility Explanation: The Data Dictionary Service Facility
command GETENTIT did not return the expected command GETENTIT did not return the expected
TABLE occurrence. If you cannot resolve this error, TABLE occurrence. If you cannot resolve this error,
contact IBM Technical Support at contact IBM Technical Support at
www.ibm.com/support. www.ibm.com/support.
-9999 ’GETPATH’ DID NOT RETURN ’FIELD’ -9999 ’GETPATH’ DID NOT RETURN ’KEY’
OCCURRENCE. PATH IS OCCURRENCE. PATH IS TABLE-KEY.
TABLE-FIELD. CHECK DATABASE CHECK DATABASE STRUCTURE.
STRUCTURE. CORRECT PROBLEM CORRECT PROBLEM AND RETRY.
AND RETRY.
Explanation: The Data Dictionary Service Facility
Explanation: The Data Dictionary Service Facility command GETPATH did not return the expected KEY
command GETPATH did not return the expected occurrence. If you cannot resolve this error, contact IBM
FIELD occurrence. If you cannot resolve this error, Technical Support at www.ibm.com/support.
contact IBM Technical Support at
www.ibm.com/support.
-9999 ’GETMORE’ DID NOT RETURN ’KEY’
OCCURRENCE. PATH IS TABLE-KEY.
-9999 ’GETMORE’ DID NOT RETURN CHECK DATABASE STRUCTURE.
’FIELD’ OCCURRENCE. PATH IS CORRECT PROBLEM AND RETRY.
TABLE-FIELD. CHECK DATABASE
Explanation: The Data Dictionary Service Facility
STRUCTURE. CORRECT PROBLEM
command GETMORE did not return the expected KEY
AND RETRY.
occurrence. If you cannot resolve this error, contact IBM
Explanation: The Data Dictionary Service Facility Technical Support at www.ibm.com/support.
command GETMORE did not return the expected
FIELD occurrence. If you cannot resolve this error,
-9999 ’DEFPATH’ FOR KEY-FIELD FAILED.
contact IBM Technical Support at
CA-DATACOM/DB REQUEST AREA
www.ibm.com/support.
RETURN CODE INFORMATION
’returncode’.
Explanation: The Data Dictionary Service Facility
command DEFPATH has failed. See the CA-Datacom
142 DB2 II System Messages for Classic Federation and Classic Event Publishing
documentation for an explanation of possible return to right beginning in the left-most position of the key. If
codes for this command. If you cannot resolve this the length of the key defined by the USE INDEX
error, contact IBM Technical Support at statement is less than the actual database key, the USE
www.ibm.com/support. INDEX defined key will be utilized as a partial (or
generic) key.
-9999 ’GETENTIT’ DID NOT RETURN ’KEY’
OCCURRENCE. PATH IS KEY-FIELD. -9999 RETURN CODE ’returncode’
CHECK DATABASE STRUCTURE. UNKNOWN. INTERNAL ERROR.
CORRECT PROBLEM AND RETRY.
Explanation: Internal error. Contact IBM Technical
Explanation: The Data Dictionary Service Facility Support at www.ibm.com/support.
command GETENTIT did not return the expected KEY
occurrence. If you cannot resolve this error, contact IBM
-9999 WARNING: COLUMN NAME
Technical Support at www.ibm.com/support.
‘column-name’ IS A DB2 RESERVED
WORD. USE QUOTES IN SQL
-9999 ’GETPATH’ DID NOT RETURN ’FIELD’ STATEMENT.
OCCURRENCE. PATH IS KEY-FIELD.
Explanation: The column-name identified in this
CHECK DATABASE STRUCTURE.
message is a reserved word. To use this column name
CORRECT PROBLEM AND RETRY.
in an SQL statement, enclose it in quotes. Checking for
Explanation: The Data Dictionary Service Facility reserved word column names and issuing this warning
command GETPATH did not return the expected message, where appropriate, is done in both USE
FIELD occurrence. If you cannot resolve this error, TABLE and USE INDEX processing.
contact IBM Technical Support at
www.ibm.com/support.
SP11 SP15
Explanation: An LU6.2 RECEIVE operation completed Explanation: An LU6.2 RECEIVE operation completed
normally but no data was received and the server has normally. The argument data buffer received was not
issued a DEALLOCATE. This means the server is not in identified correctly. Either the buffer storage was
RECEIVE mode, thereby preventing the CICS corrupted or a server did not create this buffer. The
component from returning (SENDing) any processed format and content of the data is suspect. No further
information to the server. The CICS resources have processing can be performed. This abend was issued to
been freed and this abend was issued to generate a generate a transaction dump. You must request CLOSE
146 DB2 II System Messages for Classic Federation and Classic Event Publishing
to terminate the communication session and release the program that issued this abend. No further processing
CICS resources. If the reason the buffer is incorrectly can be performed. This abend was issued to generate a
identified cannot be independently determined, contact transaction dump. You must request CLOSE to
IBM Technical Support at www.ibm.com/support. You terminate the communication session and release the
will be asked for the transaction dump and associated CICS resources. If you have recently upgraded your
output. You will also be asked for server output. installation, verify that all components have been
correctly installed. If the reason the buffer is
incompatible cannot be independently determined,
SP16
contact IBM Technical Support at
Explanation: An LU6.2 RECEIVE operation completed www.ibm.com/support. You will be asked for the
normally. The argument data buffer is not compatible transaction dump and associated output. You will also
with the communications handler service transaction be asked for server output.
Chapter 41. CICS stored procedure transaction abends (SP01 through SP16) 147
148 DB2 II System Messages for Classic Federation and Classic Event Publishing
|
CACG005I CHANGE CAPTURE SET FOR dbclass CACG105I SYSTEM CATALOG REFRESHED
TABLE creatorid.tablename
Explanation: Informational message issued by the
Explanation: Informational message issued by the correlation service. This message indicates that the
correlation service on startup. This message is issued correlation service has successfully refreshed the
for each table in the system catalog that has had metadata catalog to pick up any changes made by the
change capture activated by an ALTER command | metadata utility. This message is preceded by one or
issued in the metadata utility. more CACG005I messages to indicate the tables set for
change capture.
CACG010I RECORD SELECTION EXIT
’CACRCSEL’ INSTALLED CACG109I RECEIVING CHANGES FROM
ACTIVE | RECOVERY AGENT
| Explanation: Informational message issued by ’agentname’
| correlation service at startup. The optional record
selection exit ’CACRCSEL’ was found in the STEPLIB Explanation: Informational message issued by the
and installed. All committed transactions will be correlation service. This message indicates that the
filtered by the record selection exit. named ACTIVE or RECOVERY agent has started
sending change data to the correlation service. This
150 DB2 II System Messages for Classic Federation and Classic Event Publishing
CACG150I CORRELATION SERVER ACTIVITY CACG305I SUMMARY INFORMATION FOR IMS
REPORT AGENT IMS-Sub-System-Name Job-Name
Job-Number ASID
| Explanation: Informational message issued by the
| correlation service. This message precedes the Explanation: Informational message issued by the
correlation service metrics activity report. correlation service when monitoring for IMS changes.
This message is issued each time an active or recovery
| Following the CACG150I message, a series of
IMS change-capture agent notifies the correlation
| non-numbered WTO messages are issued that contain a
service that it is terminating. IMS change-capture agent
| correlation service metrics report. These messages
identification information consists of:
| consist of three header messages that identify
| transaction summary information that is displayed for v The IMS-Sub-System-Name of the IMS control region
| the change-capture agents being tracked by the that the agent is executing in. For IMS recovery
| correlation service. The following information is change-capture agents, this name is always
| displayed for each agent: RECOVERY.
| v Change-capture agent name | v For IMS active change-capture agents, the name of
| the job where the agent was executing. For recovery
| v Number of committed transactions (units of
| change-capture agents, this is the job name of the
| recovery) received
| active change-capture agent for which recovery is
| v Number of committed transactions sent to the | being performed.
| distribution service
v For IMS active change-capture agents, the job or
| v Number of transactions processed and confirmed by started task number where the agent was executing.
| the distribution service For an IMS recovery change-capture agent, the job
| v Number of transactions not confirmed by the number assigned to the IMS recovery change-capture
| distribution service (pending) agent.
| v State of the change-capture agent v For IMS active change-capture agents, the ASID
where the agent was executing. In recovery
situations, the ASID is the ASID assigned to the IMS
CACG151I END OF REPORT, AGENT TOTAL=’nbr recovery change-capture agent job.
of agents’
| Explanation: Informational message issued by the CACG306I BUFFERS: Buffer-Count
| correlation service. This message follows the correlation RECORDS: Record-Count
service metrics activity report. UORS: UOR-Count
COMMITS: Commit-Count
CACG152I PENDINGQ(count) MSGQ(count) ROLLBACKS Rollback-Count
UNCONFIRMED(count) Explanation: Informational message issued by the
| Explanation: Informational message issued by the correlation service when monitoring for IMS changes.
| correlation service. This message displays the number This message is issued each time an active or recovery
of transactions pending, number of data messages, and IMS change-capture agent notifies the correlation
number of unconfirmed messages. It is issued when a service that it is terminating The following information
metrics activity report is displayed by the correlation is displayed:
service. The counts in this message are a sum of counts v Buffer-Count—total number of XM data grams the
for all change-capture agents currently being monitored agent sent to the correlation service
by the correlation service. v Record-Count—total number of IMS log records that
were sent by the agent
CACG250E IDMS PRESSPACK SUPPORT IS NOT v UOR-Count—total number of UORs that were
INSTALLED processed by the correlation service for this agent
Explanation: Error message issued by the correlation v Commit-Count—total number of UORs that were
service. The IDMS Presspack software has not been committed
installed and the correlation service received a change v Rollback-Count—total number of UORs that were
to an IDMS record compressed with Presspack. The rolled back
agent is automatically placed in recovery mode, and
recovery must be done after installing Presspack
support and restarting the correlation service.
152 DB2 II System Messages for Classic Federation and Classic Event Publishing
CACG311I BUFFERS: Buffer-Count CACG314W SUMMARY INFORMATION FOR IMS
RECORDS: Record-Count AGENT IMS-Sub-System-Name Job-Name
UORS: UOR-Count Job-Number ASID
COMMITS: Commit-Count
Explanation: Warning message issued by the
ROLLBACKS Rollback-Count
correlation service, when the server is terminated and
Explanation: Informational message issued by the the server was monitoring for IMS changes. The IMS
correlation service when the server is terminated and active or recovery change-capture agent identified in
the server was monitoring for IMS changes. The the message was still active when the correlation
following information is displayed: service terminated.
v Buffer-Count—total number of XM data grams sent to IMS change-capture agent identification information
the correlation service by all IMS active consists of:
change-capture agents and all IMS recovery
v The IMS-Sub-System-Name of the IMS control region
change-capture agents that performed IMS log file
that the agent is executing in. For IMS recovery
recovery
change-capture agent, this name is always
v Record-Count—total number of IMS log records that RECOVERY.
were sent to the correlation service
v For IMS active change-capture agents, the name of
v UOR-Count—total number of UORs that were the job where the agent was executing. For recovery
processed by the correlation service | change-capture agents, this is the agent name for
v Commit-Count—total number of UORs that were | which recovery operations were being performed.
committed v For IMS active change-capture agents, the job or
v Rollback-Count—total number of UORs that were started task number where the agent was executing.
rolled back For an IMS recovery change-capture agent, the job
number assigned to the IMS recovery change-capture
agent.
CACG312I EVENTS: Event-Count
CASC: Cascade-Delete-Event-Count v For IMS active change-capture agents the ASID
DLET: Delete-Event-Count where the agent was executing. In recovery
DLLP: DLLP-Event-Count situations, the ASID is the ASID assigned to the IMS
ISRT: Insert-Event-Count recovery change-capture agent job.
REPL: Replace-Event-Count
Data server recovery is required for all active
Explanation: Informational message issued by the change-capture agents listed.
correlation service, when the server is terminated and
the server was monitoring for IMS changes. The
following information is displayed: CACG315W BUFFERS: Buffer-Count
RECORDS: Record-Count
| v Event-Count—total number of committed IMS events
UORS: UOR-Count
| received by the correlation service
COMMITS: Commit-Count
v Cascade-Delete-Count—total number of type 99 data ROLLBACKS Rollback-Count
capture log records that contained cascade delete
changes Explanation: Warning message issued by the
v Delete-Count—total number of type 99 data capture
| correlation service when the correlation service is
| terminated and the server was monitoring for IMS
log records that contained deletes
| changes and IMS agents are still active. The following
v DLLP-Event-Count—total number of type 99 data information is displayed:
capture log records that contained DLLP changes
v Buffer-Count—total number of XM data grams sent to
v Insert-Event-Count—total number of type 99 data the correlation service by the agent
capture log records that contained segment inserts
v Record-Count—total number of IMS log records that
v Replace-Event-Count—total number of type 99 data were sent to the correlation service by the agent
capture log records that contain segment updates
v UOR-Count—total number of UORs that were
processed by the correlation service for the agent
CACG313I NO IN-FLIGHT IMS UORS v Commit-Count—total number of UORs that were
Explanation: Informational message issued by the committed from the agent
correlation service, when the server is terminated and v Rollback-Count—total number of UORs that were
the server was monitoring for IMS changes. This rolled back from the agent
message indicates that at termination time there were
no in-flight IMS UOR(s) being tracked by the
correlation service.
154 DB2 II System Messages for Classic Federation and Classic Event Publishing
the likelihood of IMS generating a type 99 data capture
| CACG502I QUIESCE REQUESTED
log record marked as being in error.
| Explanation: Informational message issued by the
Receipt of a type 99 log record in error is an
| correlation service. You used the CMD interface to
unrecoverable error condition and the changes for the
| request an orderly termination of the correlation
UOR (associated with the record in error) are lost.
| service. The correlation service is in the process of
| terminating.
| CACG326W PARTIAL CHANGE DISCARDED
| Explanation: Warning message issued by the CACG801W CORRELATION SERVICE
| correlation service when receiving changes from an TERMINATING
| active IMS change-capture agent. This message is
Explanation: A warning issued by the correlation
| informing you that you have either COLD started the
service on shutdown. The correlation service is
| correlation service or used the IMS recovery
stopping either in response to an operator STOP
| change-capture agent to place an IMS agent back into
command or due to a processing error that prohibits
| active mode. The correlation service has received an
continuing to service change-capture agents. All known
| IMS type 99 data capture log record for a UOR that is
agents are placed in recovery mode unless they have
| not currently being tracked, however, the type 99 data
successfully informed the correlation service of a
| capture log record contains the second part of a partial
shutdown and they have no pending or unconfirmed
| change. The first part of the change has been lost and
change messages.
| occurred before you forced the IMS change-capture
| agent back into active mode.
CACG802I CORRELATION SERVICE QUIESCING
| This message is identifying that you have lost IMS
| data. Because you forced the agent back to active Explanation: Informational message issued by the
| mode, this is not an error. correlation service on shutdown. The correlation service
is stopping and there are outstanding messages that
have not been confirmed. The correlation service
| CACG501E Command IS NOT A VALID
automatically stops receiving any new messages or
| COMMAND
forwarding pending messages. In quiesce mode, the
| Explanation: Error message issued by the correlation correlation service waits until the publication service
| service. An unknown command was issued using the either disconnects or until all unconfirmed messages
| CMD operator interface. Supply a valid command and are confirmed. While quiescing will not prevent forcing
| try again. agents into recovery mode, it attempts to keep agents
from being left in-doubt at shutdown.
156 DB2 II System Messages for Classic Federation and Classic Event Publishing
CACH017W SHUTDOWN CORRELATION SERVER CACH022E IMS change-capture agent ABENDED
IS NOT ACTIVE
Explanation: Error message issued by the IMS Logger
Explanation: Warning issued by the shutdown Exit (DFSFLGX0) when it is notified of an abend in
notification program CACE1TRM. The shutdown DB2 Information Integrator code. This message is
message was not sent to the correlation service because accompanied by standard MVS WTO messages
there is no active correlation service. This indicates that identifying the type of abend and the contents of the
the correlation service was never started or was registers at abend.
shutdown prior to shutting down the database system.
Control is immediately returned to IMS. The IMS active
Stopping a correlation service without first stopping the
change-capture agent has deactivated itself and does
database system will force the agent into recovery
not attempt to inform the correlation service that it is in
mode.
recovery mode. Contact IBM Technical Support at
www.ibm.com/support.
CACH018E SHUTDOWN ERROR(n) IN
LOCATING CORRELATION SERVER
CACH023E IMS change-capture agent STORAGE
Explanation: Error message issued by the shutdown ALLOCATION FAILED
notification program CACE1TRM. An unexpected error
Explanation: Error message issued by the IMS Logger
occurred while locating and active correlation service.
Exit (DFSFLGX0) when the exit attempted to allocate
Contact IBM Technical Support at
storage to communicate with the correlation service out
www.ibm.com/support.
of sub-pool 132. The amount of storage requested was
not available.
CACH019E SHUTDOWN VMNOTIFY FAILURE
Control is immediately returned to IMS. The IMS active
RC(nn,xxxxxxxx)
change-capture agent has deactivated itself and does
Explanation: Error message issued by the shutdown not attempt to inform the correlation service that it is in
notification program CACE1TRM. An unexpected error recovery mode. Contact IBM Technical Support at
occurred in communicating with an active correlation www.ibm.com/support.
service. Contact IBM Technical Support at
www.ibm.com/support. Be prepared to provide the RC
CACH024E XM DATAGRAM FAILED; SEE
information.
SYSTEM MESSAGE = 0X(nnnnnnnn)
REASON CODES (nnnnnnnn,
CACH020I SHUTDOWN COMPLETED nnnnnnnn)
SUCCESSFULLY
Explanation: Error message issued by the IMS Logger
Explanation: Informational message issued by the Exit (DFSFLGX0) when it attempted to communicate
shutdown notification program CACE1TRM. The with the correlation service. The error message is
shutdown notification program successfully sent a displayed in hexadecimal format. Refer to the
shutdown message to the correlation service. The appropriate section of this guide for an explanation of
correlation service issues the message CACG114I to the messages number being reported.
indicate the message was received.
When this error is reported, the IMS Logger Exit
attempts to notify the correlation service that this IMS
CACH021E UNKNOWN LOGGER EXIT active change-capture agent is now in recovery mode.
FUNCTION
Explanation: Error message issued by the IMS Logger CACH025E LOAD VECTOR TABLE ERROR
Exit (DFSFLGX0) when it is passed an unknown RC(General-Return-Code,Specific-Return-
processing function code. This message indicates that Code)
either the interface to the IMS Logger Exit has been
Explanation: Error message issued by the IMS
modified or that some form of system corruption has
recovery change-capture agent. An unexpected error
occurred.
occurred while initializing the recovery change-capture
Control is immediately returned to IMS. The IMS active agent. Contact IBM Technical Support at
change-capture agent has deactivated itself and does www.ibm.com/support. Be prepared to provide the RC
not attempt to inform the correlation service that it is in information.
recovery mode. Contact IBM Technical Support at
www.ibm.com/support.
Supply a valid input control card file and run the IMS Start the correlation service, wait for the server ready
recovery change-capture agent again. WTO message, and then resubmit the IMS recovery
change-capture agent.
158 DB2 II System Messages for Classic Federation and Classic Event Publishing
| The message identifies a 16-byte hexadecimal number
CACH034E Function ERROR SERVICE ‘Service-Name’
| representing the system store clock where restart is to
RC(General-Return-Code,Specific-Return-
Code)
| begin.
Explanation: Error message issued by the IMS Each IMS log record contains a suffix that consists of
recovery change-capture agent when attempting to the 8-byte system store clock value of when the log
communicate with the named service identified by record was created and an 8-byte double word log
Service-Name. Function identifies the type of sequence number. The initial IMS log file supplied for
communication attempted and General-Return-Code and an agent in recovery should have a store clock value
Specific-Return-Code identify the error code returned. less than the Store-Clock-Value, and the last record in the
Contact IBM Technical Support at file must contain a store clock value greater than
www.ibm.com/support. Be prepared to provide the full Store-Clock-Value. All subsequent log files first log
message text for problem resolution. record must have a store clock that is greater than the
Store-Clock-Value.
CACH035E NO RECOVERY INFORMATION FOR
AGENT ‘Agent-Name’ If this message was issued in conjunction with message
CACH036I, then identify the correct IMS log files
Explanation: Error message issued by the IMS required to recover Agent-Name and then run the IMS
recovery change-capture agent when attempting to recovery change-capture agent again. Otherwise this is
retrieve restart information for an IMS active an informational message that is identifying the restart
change-capture agent that is marked as being in point in the IMS log files for an agent in recovery
recovery. Contact IBM Technical Support at mode.
www.ibm.com/support.
CACH038I RESTART LOG SEQ. #
CACH036E AGENT ‘Agent-Name’ RESTART POINT High-Order-Word-Low-Order-Word
NOT FOUND
Explanation: Informational message issued by the IMS
Explanation: Error message issued by the IMS recovery change-capture agent when:
recovery change-capture agent. This message is issued v The initial restart point, for an agent in recovery
during IMS log file recovery processing when the IMS cannot be found in the IMS log files supplied.
recovery change-capture agent is attempting to locate
the restart point for Agent-Name for the IMS log files v The IMS recovery change-capture agent is checking
that were supplied for the agent. This message is an agent’s recovery status, and the correlation service
followed by messages CACH037I and CACH038I, knows the agent is in recovery mode.
which identify the restart point that was being v The IMS recovery change-capture agent is placing an
searched. agent in recovery mode.
The general implication of this message is that the
| The message identifies a double word hexadecimal
correct IMS log files were not supplied for Agent-Name.
| number identifying the IMS log record where restart is
The IMS log files supplied are “too old,” and only
| to begin.
contain IMS log records that were created prior to the
current restart point. Ensure that you supply IMS log
Each IMS log record contains a suffix that consists of
files that include records created before, and including
the 8-byte system store clock value of when the log
the restart point and after the restart point. Run the
record was created as well as an 8-byte double word
IMS recovery change-capture agent again after
log sequence number. The initial IMS log file supplied
identifying to correct IMS log files to use as input.
for an agent in recovery should have a store clock
value less than the Store-Clock-Value displayed in
| CACH037I RESTART SYSTEM CLOCK message CACH037I and a log sequence number that is
| Store-Clock-Value less than the number identified in this message. Also,
the last record in the file must contain a store clock
Explanation: Informational message issued by the IMS
value greater than Store-Clock-Value and a log sequence
recovery change-capture agent when:
number greater than the one displayed in message
v The initial restart point, for an agent in recovery CACH038I.
cannot be found in the IMS log files supplied.
v The IMS recovery change-capture agent is checking Depending on the IMS control region type, log record
an agent’s recovery status, and the correlation service sequence numbers may continue ascending between
knows that the agent is in recovery mode. log files or may restart from 1 or some other number.
v The IMS recovery change-capture agent is placing an All subsequent log files’ first log record must have a
agent in recovery mode. store clock that is greater than the Store-Clock-Value
displayed in message CACH037I.
160 DB2 II System Messages for Classic Federation and Classic Event Publishing
the file does not exist. In this situation, update the
CACH053I AGENT ‘Agent-Name’ IS ALREADY IN
input control file and specify the name of an existing
RECOVERY MODE
recovery dataset. For other errors, contact IBM
Technical Support at www.ibm.com/support. Explanation: Informational message issued by the IMS
recovery change-capture agent when placing unknown
agents into recovery mode. This message indicates that
CACH048I RECOVERY DATASET File-Name
the correlation service has already marked Agent-Name
OPENED
as being in recovery mode. No action is required.
Explanation: Informational message issued by the IMS
recovery change-capture agent when a recovery dataset
CACH054I PREPARING TO ACTIVATE AGENT
(identified by File-Name) is successfully opened. When
‘Agent-Name’
this message is issued, it means that the associated IMS
active change-capture agent (identified by message Explanation: Informational message issued by the IMS
CACH049I) needs to be placed into recovery mode and recovery change-capture agent when placing one or
that the recovery dataset contains recovery restart point more agents that are in recovery mode back into active
information. mode. Agent-Name identifies an agent that is in
recovery mode that the IMS recovery change-capture
agent is ready to start placing back into active mode.
CACH049I AGENT NAME IS ‘Agent-Name’
No action is required.
Explanation: Informational message issued by the IMS
recovery change-capture agent when it is working with
CACH055I STARTING LOG FILE SEQUENCE
recovery datasets. It identifies the name of the IMS
CHECKING
active change-capture agent associated with a recovery
dataset that contains recovery information. No action is Explanation: Informational message issued by the IMS
required. recovery change-capture agent when performing IMS
log file recovery. This message is issued after all control
file input has been read and communications have been
CACH050I RECOVERY DATASET File-Name
established with the correlation service.
REPORTS AGENT IS NOT IN
RECOVERY MODE Depending upon how many agents and how many IMS
log files have been supplied, it may take some time
Explanation: Informational message issued by the IMS
before message CACH058I is issued identifying that log
recovery change-capture agent when it is checking
file sequence checking has completed successfully.
agents’ recovery status. When issued, this message
indicates that the recovery dataset identified by If you supply more than one IMS log file for an agent,
File-Name is empty, and, therefore, according to the or request incremental recovery for one or more agents,
recovery dataset, the IMS active change-capture agent the IMS recovery change-capture agent scans each IMS
associated with the recovery dataset is not in recovery log file to perform sequence number checking and log
mode. No action is required. file resequencing to get the files in their proper
processing order. No action is required.
CACH051I CORRELATION SERVER REPORTS
AGENT IN RECOVERY MODE CACH056E AGENT ‘Agent-Name’ DUPLICATE LOG:
IMS-Log-File-Name
Explanation: Informational message issued by the IMS
recovery change-capture agent when it is checking Explanation: Error message issued by the IMS
agents’ recovery status. When issued, this message recovery change-capture agent when performing IMS
indicates that the correlation service does not consider log file recovery. During sequence checking, the IMS
the agent (identified in message CACH049I) to be in recovery change-capture agent has identified
recovery mode. No action is required. IMS-Log-File-Name is duplicated for Agent-Name.
Delete the control card identified from the input control
CACH052I AGENT ‘Agent-Name’ IS NOW IN file and run the IMS recovery change-capture agent
RECOVERY MODE again.
Explanation: Informational message issued by the IMS
recovery change-capture agent when placing unknown CACH057E AGENT ‘Agent-Name’ INVALID LOG:
agents into recovery mode. This message indicates that IMS-Log-File-Name
the correlation service has been notified that
Explanation: Error message issued by the IMS
Agent-Name is now in recovery mode. No action is
recovery change-capture agent when performing IMS
required.
log file recovery. During sequence checking the IMS
recovery change-capture agent has identified
IMS-Log-File-Name for Agent-Name contains starting or
No action is required.
162 DB2 II System Messages for Classic Federation and Classic Event Publishing
CACH065E UNRECOGNIZED PARAMETER CACH070I LOG TRACKING FILE IS EMPTY
‘Parameter-Name’
Explanation: Informational message issued by the IMS
Explanation: Error message issued by the IMS recovery change-capture agent when checking agent
recovery change-capture agent while parsing the recovery mode status (and the agent is in recovery
command line input. Parameter-Name is not a valid mode) or when placing an unknown agent in recovery
command line parameter. mode.
Review the IMS recovery change-capture agent This message is issued when IMS log file tracking has
documentation for a description of the command line been implemented, but there is no IMS log file
parameters and parameter values. Modify the information in the tracking data set. You must
command line input to supply valid values, and then manually identify the IMS log files that are required in
rerun the IMS recovery change-capture agent. the IMS log file recovery process.
CACH067I LOG TRACKING FILE DOES NOT CACH071I Number IMS AGENTS ARE IN
EXIST RECOVERY MODE
Explanation: Informational message issued by the IMS Explanation: Informational message issued by the IMS
recovery change-capture agent when checking the recovery change-capture agent when checking agent
recovery status of an agent. The IMS active recovery mode status and agents are in recovery.
change-capture agent identified in message CACH049I Number identifies how many agents are in recovery
has not implemented IMS log file tracking. Because mode.
there is no IMS log file tracking information available,
you must manually identify the IMS log files that are
required in the IMS log file recovery process.
| CACH072I BUFFERS SENT Buffer-Count RECORDS
| Record-Count THROTLES Throttle-Count
Explanation: Informational message issued by the IMS
CACH068I INPUT LOG FILE IMS-Log-File-Name
recovery change-capture agent during termination
Explanation: Informational message issued by the IMS processing when performing IMS log file recovery with
recovery change-capture agent when checking agent the following values:
recovery mode status (and the agent is in recovery v Buffer-Count: Identifies the number of data grams
mode) or when placing an unknown agent in recovery | sent to the correlation service.
mode.
v Record-Count: Identifies the number of data capture
This message is issued when IMS log file tracking has and sync-point log records sent to the correlation
been implemented. IMS-Log-File-Name identifies the service for analysis and processing.
fully-qualified IMS log file that needs to be supplied as v Throttle-Count: Identifies the number of times the
input to the IMS log file recovery process. correlation service was pinged to determine whether
it was still responding. No action required.
| CACH069I POTENTIALLY-NECESSARY LOG FILE
| IMS-Log-File-Name | CACH073E AGENT Agent-Name INVALID BATCH
Explanation: Informational message issued by the IMS | LOG: IMS-Log-File-Name
recovery change-capture agent when checking agent | Explanation: Error messages issued by the IMS
recovery mode status (and the agent is in recovery | recovery change-capture agent. The IMS log file
mode) or when placing an unknown agent in recovery | identified by IMS-Log-File-Name was not created by the
mode. | IMS sub-system identified by Agent-Name. Remove the
This message is issued when IMS log file tracking has | reference to the invalid IMS log file and ensure that the
been implemented. IMS-Log-File-Name identifies the | correct IMS log files are referenced before re-running
fully-qualified IMS log file that may need to be | the IMS recovery change-capture agent.
supplied as input to the IMS log file recovery process.
The identified IMS log file is required if the log file | CACH074E AGENT Agent-Name INVALID ONLINE
ending date/time is after the restart time identified in | LOG: IMS-Log-File-Name
message CACH040I. If you are not sure when the IMS
log file was closed, supplying the name of | Explanation: Error messages issued by the IMS
IMS-Log-File-Name during the IMS log file recovery | recovery change-capture agent. The IMS log file
process will ensure that all IMS log files that are | identified by IMS-Log-File-Name was not created by the
required have been identified. | IMS sub-system identified by Agent-Name. Remove the
| reference to the invalid IMS log file and ensure that the
| correct IMS log files are referenced before re-running
| the IMS recovery change-capture agent.
| CACH077I AGENT Agent-Name INVALID ONLINE Increase the REGION size on the EXEC JCL statement
| LOG: IMS-Log-File-Name and run the IMS Log File Tracking Utility again.
CACH080W LOG FILE DOES NOT EXIST CACH085W LOG FILE TRACKING UTILITY
IMS-Log-File-Name COMPLETED WITH WARNINGS
Explanation: Warning message issued by the IMS Log Explanation: Warning message issued by the IMS Log
File Tracking Utility. IMS-Log-File-Name does not exist. File Tracking Utility. Indicates that log tacking
This is most likely a JCL error or an invalid reference to information could not be obtained for one of the IMS
a generation data set. Verify that the JCL is referencing log files identified. This is generally a setup error.
the correct IMS log file(s). Review the JCL and ensure that the proper IMS log
files are being referenced.
CACH081E LOG FILE Function ERROR FOR
IMS-Log-File-Name ERRNO: Error CACH085E LOG FILE TRACKING UTILITY
Explanation: Error message issued by the IMS Log ENDED IN ERROR
File Tracking Utility. An error was reported when Explanation: Error message issued by the IMS Log
IMS-Log-File-Name was opened or read (identified by File Tracking Utility when an error is detected. Refer to
Function). The SAS/C error number is identified by prior error messages in order to identify and resolve
Error. the problem.
This is an internal error. Contact IBM Technical Support
at www.ibm.com/support. | CACH098I IMS TERMINATION NOTIFICATION
| RECEIVED
CACH082E NO USABLE LOG FILES FOUND | Explanation: Informational message issued by the IMS
Explanation: Error message issued by the IMS Log | active change-capture agent (IMS Logger Exit -
File Tracking Utility. No IMS log file information was | DFSFLGX0) indicating that IMS is terminating. No
captured in this run of the IMS Log File Tracking | action is required.
Utility. This is generally a setup error. Verify that the
164 DB2 II System Messages for Classic Federation and Classic Event Publishing
Specify a valid APPLID, and restart the CICS VSAM
| CACH099I SENDING IMS TERMINATION
agent.
| NOTIFICATION
| Explanation: Informational message issued by the IMS
CACH105I CICS VSAM CAPTURE: v.r.m
| active change-capture agent (IMS Logger Exit -
mmddyyyy READY
| DFSFLGX0) indicating that the correlation service is
| being notified of IMS is termination. No action is | Explanation: Informational message issued by the
| required. | VSAM change-capture agent. The CICS VSAM agent
has completed initialization and is active. v is the
| If message CACH098I is issued and message
version, r the release, m the modification level and
| CACH099I is not issued, the IMS active change-capture
mmddyyyy the date of the CICS VSAM agent.
| agent for this IMS sub-system is in recovery mode at
| the time of IMS termination.
CACH106I START PROCESSING AT mm/dd/yyyy
hh:mm:ss START PROCESSING FOR
CACH101E INVALID STREAM NAMES
logstream AT mm/dd/yyyy hh:mm:ss
SPECIFIED ON THE SERVICE INFO
ENTRY | Explanation: Informational message issued by the
| VSAM change-capture agent. Identifies that processing
| Explanation: Error message issued by the VSAM
| is beginning at the requested date and time in the log
| change-capture agent. A log stream was not specified
| stream.
on field 10 of the SERVICE INFO ENTRY for the CICS
VSAM agent, or only one log stream was specified, or
more than two log streams were specified and the Log CACH107W REQUESTED START PROCESSING AT
of Logs log stream was not one of them. mm/dd/yyyy hh:mm:ss
Specify a log stream on field 10 of the SERVICE INFO | Explanation: Warning message issued by the VSAM
ENTRY. The system log stream and one user log stream | change-capture agent. The data for the requested start
must be specified. More than one user log streams can time was not available, or the STARTUP option was
be specified, but the Log of Logs log stream must also specified and data when CICS started is not available.
be specified. The oldest available data will be used as the start time
and identified in message CACH106I.
CACH102E INVALID START DATE SPECIFIED ON
THE SERVICE INFO ENTRY | CACH108W WAITING FOR CONNECTION TO
| THE CORRELATION SERVICE
| Explanation: Error message issued by the VSAM
| change-capture agent. A start option of TIME was | Explanation: Warning message issued by the VSAM
specified on field 10 of the SERVICE INFO ENTRY for | change-capture agent. The CICS VSAM agent is waiting
the CICS VSAM agent, but the date specified was not a for the correlation service to activate.
valid date.
| If the correlation service is activated before the VSAM
Specify a valid start date, and restart the CICS VSAM | change-capture agent and this message is issued,
agent | generally, this means that the wrong communications
| protocol/information was supplied for the VSAM
CACH103E INVALID START TIME SPECIFIED ON
| change-capture agent's SIE definition. In this situation,
| stop the server and ensure that the correlation service
THE SERVICE INFO ENTRY
| and VSAM change-capture agent SIE definitions are in
| Explanation: Error message issued by the VSAM | sync.
| change-capture agent. A start option of TIME was
specified on field 10 of the SERVICE INFO ENTRY for
CACH109E DATA NOT AVAILABLE TO START
the CICS VSAM agent, but the time specified was not a
RECOVERY AT mm/dd/yyyy hh:mm:ss
valid time.
Specify a valid start time, and restart the CICS VSAM
| Explanation: Error message issued by the VSAM
| change-capture agent. The data for the last recovery
agent
point is not available in the log streams. A cold start of
the CICS VSAM agent must be done.
CACH104E INVALID APPLID SPECIFIED ON THE
SERVICE INFO ENTRY
CACH110I CICS VSAM AGENT COLD
| Explanation: Error message issued by the VSAM STARTING
| change-capture agent. An APPLID qualifier was
specified on field 10 of the SERVICE INFO ENTRY for
| Explanation: Informational message issued by the
| VSAM change-capture agent. The CICS VSAM agent is
the CICS VSAM Agent, but the APPLID was not
specified or was more than eight characters in length.
166 DB2 II System Messages for Classic Federation and Classic Event Publishing
| CACH312E CORRELATION SERVICE IS NOT CACH318E AGENT agentname ERROR OPENING
| ACTIVE JOURNAL n
Explanation: Error message issued by the CA-IDMS Explanation: Error message issued by the CA-IDMS
recovery change-capture agent. Recovery is not possible recovery change-capture agent. A failure occurred when
because there is no correlation service currently opening one of the journal files allocated to the
running on the system. A correlation service must be recovery process. The journal number nn equates to the
started before recovery is possible. DD name JnJRNL in the recovery JCL. Verify that the
file allocated to JnJRNL is correct. If you need
additional assistance, contact IBM Technical Support at
CACH313E ERROR IN CSA RC(nn)
www.ibm.com/support.
Explanation: Error message issued by the CA-IDMS
recovery change-capture agent. An error was detected
CACH319E AGENT agentname IDMSJNL2 ERROR
in common storage. Contact IBM Technical Support at
RC(nn)
www.ibm.com/support. Be prepared to provide the RC
value for problem diagnosis. Explanation: Error message issued by the CA-IDMS
recovery change-capture agent. A call to the module
IDMSJNL2 failed when issued by the recovery
CACH314I AGENT agentname RETURNING TO
change-capture agent. Contact IBM Technical Support
ACTIVE MODE
at www.ibm.com/support.
Explanation: Informational message issued by the
CA-IDMS recovery change-capture agent. The recovery
CACH320I RECOVERY JOURNAL SEQUENCE IS
change-capture agent is placing the named
xxxxxxxx xxxxxxxx TIMESTAMP
change-capture agent back in active mode.
hh:mm:ss
Explanation: Informational message issued by the
CACH315E function ERROR SERVICE
CA-IDMS recovery change-capture agent. This message
’servicename’ nn RC(nn,xxxxxxxx)
informs the user of the record sequence number and
Explanation: Error message issued by the CA-IDMS internal database timestamp associated with the restart
recovery change-capture agent. A communications point for recovery purposes. This information is
function failed for the named service. Contact IBM particularly useful in determining an archive tape or
Technical Support at www.ibm.com/support. file when recovery must be done from a historical
archive.
CACH316E NO RECOVERY INFO FOR AGENT
agentname CACH321E NAME TOKEN CALL FAILED RC(n)
Explanation: Error message issued by the CA-IDMS Explanation: Error message issued by the CA-IDMS
recovery change-capture agent. The correlation service | recovery change-capture agent. A call to z/OS name
has no recovery information for the named agent. token services failed. Contact IBM Technical Support at
Recovery is not possible without recovery information www.ibm.com/support.
for restart purposes. Run the recovery change-capture
agent with ACTIVATE=Y to return to active mode if
CACH322I RECOVERY STARTING FROM
applicable.
JOURNAL nn RECORD nn
Explanation: Informational message issued by the
CACH317E AGENT agentname RESTART SEQ
CA-IDMS recovery change-capture agent. This message
xxxxxxxx xxxxxxxx NOTFND
informs the user where in the CV journals the recovery
Explanation: Error message issued by the CA-IDMS sequence number was found. By comparing this
recovery change-capture agent. The journal sequence information to the current journal position of the IDMS
number used as a restart point for recovery purposes CV, you can determine how much change data must be
was not found in the journal files passed to the processed for the recovery change-capture agent to
recovery change-capture agent. If recovering in CV catch up to the current record in the online journals. To
mode, the restart point may have already been display the current position in online journals, issue the
overwritten by normal C journaling. In this case, IDMS DCMT DISPLAY JOURNALS command.
recovery must be done from an archive journal.
CACH323I PROCESSING JOURNAL FILE JnnJRNL
Explanation: Informational message issued by the
CA-IDMS recovery change-capture agent. This message
informs the user when a new journal file is being
processed by the recovery change-capture agent. By
CACH328E SEQUENCE ERROR PROCESSING | Explanation: Error message issued by the correlation
JOURNAL FILE | service when monitoring for CA-IDMS changes. This
| message is issued when an IDMS change-capture agent
Explanation: The CA-IDMS recovery change-capture | terminates and the correlation service was tracking an
agent discovered a sequence error in the journal file | in-flight UOR at the time the IDMS change-capture
and terminated processing. A sequence error results | agent terminated. Recovery is required for the agent
when the journal files are incorrectly allocated to the | identified in message CACH340I.
recovery change-capture agent job. Either the journal
files are out of order or a journal file is missing.
CACH350I RECOVERY PROCESSING
COMPLETED SUCCESSFULLY
Explanation: Message issued by the CA-IDMS
recovery change-capture agent at completion of
168 DB2 II System Messages for Classic Federation and Classic Event Publishing
processing. This message indicates that recovery
| CACJ001E Command IS NOT A VALID
processing was successful.
| COMMAND
| Explanation: Error message issued by the publication
CACH350W RECOVERY PROCESSING ENDED
| service when an invalid CMD,Publication-Service-
WITH WARNINGS
| Name command is issued. Command identifies the
Explanation: Error message issued by the CA-IDMS | invalid keyword that was specified. Correct the
recovery change-capture agent at completion of | command and re-issue.
processing. This message indicates that the recovery
process ended with one or more warnings.
| CACJ002I QUIESCE REQUESTED
| Explanation: Informational message issued by the
CACH350E RECOVERY PROCESSING ENDED IN
| publication service in response to a
ERROR
| CMD,Publication-Service-Name,QUIESCE command.
Explanation: Error message issued by the CA-IDMS | The publication service has initiated an order
recovery change-capture agent at completion of | shutdown.
processing. This message indicates that recovery was
not successful.
These messages are generated by the data server and appear in the system log. If
an undocumented error is returned, contact IBM Technical Support at
www.ibm.com/support for assistance.
LSCX012 Unable to load runtime I/O routines, LSCXnnn ERRNO = EACCES Inaccessible
execution cannot continue. socket/file or permission denied.
Explanation: The SAS/C library must be Explanation: Verify that the socket specified in the
APF-authorized. Make sure this library is data server configuration is within the is within the
APF-authorized before continuing. If it is range that has been assigned to the server and that the
APF-authorized, use the F servername, DISPLAY, ALL data server/userid has the proper security access for
command to determine that the region size in which the file specified in the error message.
the server is running is at least 2MB greater than the
MESSAGE POOL SIZE specified in the data server
LSCXnnn ERRNO = EADDRINUSE Socket
configuration.
address already in use.
Explanation: Verify that the socket specified in the
LSCX503 Warning. Errno=ENFOUND. File never
data server configuration is not allocated to another
created, open failed. Interrupted while:
task and that you have not specified a value greater
Opening file "ddn:CACTAB or
than the one for the value of the maximum tasks for a
CACCOL".
connection handler SIE entry.
Explanation: Informational message that occurs if the
metadata files (used by the metadata utility) are empty.
LSCXnnn ERRNO = EADDRNOTAVAIL Socket
The catalog information is still created and functional.
address is not available.
Explanation: Verify that the socket specified in the
LSCX550 Warning. ERRNO=ENOSPC. Record not
data server configuration is a valid socket address.
written, file is full.
Explanation: Logger has run out of space and will
LSCXnnn ERRNO = EALREADY Previous
stop writing messages. The data server remains
connection not yet completed.
functional but more space is needed for the logger task.
Explanation: Verify that the socket specified in the
data server configuration is not in use.
LSCX1210
Explanation: Internal error. Contact the system
LSCXnnn ERRNO = ECONNABORTED
administrator.
Connection aborted by local software.
Explanation: Verify that communication software is
LSCXnnn ****WARNING**** ERRNO =
available and that the data server can access it.
XXXXXXXX
Explanation: Check the following entries for ERRNO
LSCXnnn ERRNO = ECONNREFUSED
messages, definitions, and actions. Use the NETSTAT
Destination host refused connection.
SOCKET, PING, and T4RACERTE commands to
determine TCP/IP connection availability. Display the Explanation: Verify that the socket specified in the
status of the APPLID (LU) using VTAM/NETVIEW or data server configuration is within the range that has
SNA server/comm server commands to determine SNA been assigned to the server.
connection availability.
LSCXnnn ERRNO = EHOSTDOWN Destination LSCXnnn ERRNO = ENOENT File or directory not
host is down. found.
Explanation: Verify that the destination host and its Explanation: Verify that the file or directory name
communication software are active and ready to accept displayed in the error message exists and is valid.
connections.
LSCXnnn ERRNO = ENOMEM Insufficient
LSCXnnn ERRNO = EHOSTUNREACH memory.
Destination host is unreachable.
Explanation: Insufficient memory. Shut down some of
Explanation: Verify that the destination host and its the active programs or increase the region size.
communication software are active and ready to accept
connections.
LSCXnnn ERRNO = ENOSPC No space in file.
Explanation: Verify that the file displayed has not
LSCXnnn ERRNO = EINUSE File to be opened
exceeded 16 extents, space available within the
was already in use.
volume/HSM storage class.
Explanation: Verify that the file specified in the error
message is not in use by another task.
LSCXnnn ERRNO = ENOTCONN Socket is not
connected.
LSCXnnn ERRNO = EISCONN Socket is already
Explanation: Verify that the communication software
connected.
on the host to which you are connecting is active and
Explanation: Verify that the socket specified in the ready to accept connections.
data server configuration is valid and not duplicated
for multiple entries. Verify that the value of the
LSCXnnn ERRNO = EPREV Previous error is not
maximum tasks for the connection handler SIE is not
cleared up.
greater than one.
Explanation: Contact IBM Technical Support at
www.ibm.com/support.
LSCXnnn ERRNO = ENAMETOOLONG Filename
too long.
LSCXnnn ERRNO = ESHUTDOWN Connection
Explanation: Verify that the file name in the error
has been shutdown.
message does not violate file naming conventions.
Explanation: Connection has been shut down by
remote host. Verify that the communication software on
LSCXnnn ERRNO = ENETDOWN Local host’s
the remote host is active and ready to accept
network down or inaccessible.
connections before proceeding.
Explanation: Verify connectivity to the remote host.
172 DB2 II System Messages for Classic Federation and Classic Event Publishing
host is active and ready to accept connections.
LSCXnnn ERRNO = ETIMEOUT Socket
connection timed-out.
Explanation: Retry operation. If problem persists,
verify that the communication software on the remote
For more information on SAS/C error messages, see the SAS/C Web site at www.sas.com.
To access the latest DB2 Information Integrator product documentation, from the
DB2 Information Integrator Support Web site, click on the Product Information
link, as shown in Figure 1 on page 176.
You can access the latest DB2 Information Integrator documentation, in all
supported languages, from the Product Information link:
v DB2 Information Integrator product documentation in PDF files
v Fix pack product documentation, including release notes
v Instructions for downloading and installing the DB2 Information Center for
Linux, UNIX, and Windows
v Links to the DB2 Information Center online
Scroll though the list to find the product documentation for the version of DB2
Information Integrator that you are using.
176 DB2 II System Messages for Classic Federation and Classic Event Publishing
The DB2 Information Integrator Support Web site also provides support
documentation, IBM Redbooks, white papers, product downloads, links to user
groups, and news about DB2 Information Integrator.
You can also view and print the DB2 Information Integrator PDF books from the
DB2 PDF Documentation CD.
178 DB2 II System Messages for Classic Federation and Classic Event Publishing
Table 3. DB2 Information Integrator documentation about event publishing function for IMS
and VSAM on z/OS (continued)
Form
Name number Location
Planning Guide for Event Publisher for z/OS SC18-9158 DB2 Information Integrator
Support Web site
Reference for Classic Federation and Event SC18-9156 DB2 Information Integrator
Publisher for z/OS Support Web site
System Messages for Classic Federation and SC18-9162 DB2 Information Integrator
Event Publisher for z/OS Support Web site
Release Notes for IBM DB2 Information N/A DB2 Information Integrator
Integrator Event Publisher for IMS for z/OS Support Web site
Release Notes for IBM DB2 Information N/A DB2 Information Integrator
Integrator Event Publisher for VSAM for z/OS Support Web site
180 DB2 II System Messages for Classic Federation and Classic Event Publishing
Table 6. DB2 Information Integrator documentation about federated function on Linux, UNIX,
and Windows (continued)
Form
Name number Location
C++ API Reference for Developing Wrappers SC18-9172 v DB2 PDF Documentation CD
v DB2 Information Integrator
Support Web site
Data Source Configuration Guide N/A v DB2 PDF Documentation CD
v DB2 Information Integrator
Support Web site
Federated Systems Guide SC18-7364 v DB2 PDF Documentation CD
v DB2 Information Integrator
Support Web site
Guide to Configuring the Content Connector for N/A DB2 Information Integrator
VeniceBridge Support Web site
Installation Guide for Linux, UNIX, and GC18-7036 v DB2 PDF Documentation CD
Windows
v DB2 Information Integrator
Support Web site
Java API Reference for Developing Wrappers SC18-9173 v DB2 PDF Documentation CD
v DB2 Information Integrator
Support Web site
Migration Guide SC18-7360 v DB2 PDF Documentation CD
v DB2 Information Integrator
Support Web site
Wrapper Developer’s Guide SC18-9174 v DB2 PDF Documentation CD
v DB2 Information Integrator
Support Web site
Release Notes for IBM DB2 Information N/A v In the DB2 Information
Integrator Standard Edition, Advanced Edition, Center, Product Overviews
and Replication for z/OS > Information Integration >
DB2 Information Integrator
overview > Problems,
workarounds, and
documentation updates
v DB2 Information Integrator
Installation launchpad
v DB2 Information Integrator
Support Web site
v The DB2 Information
Integrator product CD
182 DB2 II System Messages for Classic Federation and Classic Event Publishing
Table 8. DB2 Information Integrator Release Notes and Installation Requirements (continued)
Name File name Location
Release Notes for IBM DB2 N/A DB2 Information Integrator Support
Information Integrator Event Web site
Publisher for VSAM for z/OS
Release Notes for IBM DB2 N/A DB2 Information Integrator Support
Information Integrator Classic Web site
Federation for z/OS
Release Notes for Enterprise Search N/A DB2 Information Integrator Support
Web site
To view the installation requirements and release notes that are on the product CD:
v On Windows operating systems, enter:
x:\doc\%L
x is the Windows CD drive letter and %L is the locale of the documentation that
you want to use, for example, en_US.
v On UNIX operating systems, enter:
/cdrom/doc/%L/
cdrom refers to the UNIX mount point of the CD and %L is the locale of the
documentation that you want to use, for example, en_US.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country/region or send inquiries, in
writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country/region where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions; therefore, this statement may not apply
to you.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product, and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious, and any similarity to the names and addresses used by an actual
business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
186 DB2 II System Messages for Classic Federation and Classic Event Publishing
Each copy or any portion of these sample programs or any derivative work must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights
reserved.
Trademarks
The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
IBM
AIX
CICS
DB2
DB2 Universal Database
Hiperspace
IMS
MVS
POWER
RACF
VTAM
WebSphere
z/OS
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation
in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Notices 187
188 DB2 II System Messages for Classic Federation and Classic Event Publishing
Contacting IBM
To contact IBM customer service in the United States or Canada, call
1-800-IBM-SERV (1-800-426-7378).
To learn about available service options, call one of the following numbers:
v In the United States: 1-888-426-4343
v In Canada: 1-800-465-9600
To locate an IBM office in your country or region, see the IBM Directory of
Worldwide Contacts on the Web at www.ibm.com/planetwide.
Product information
Information about DB2 Information Integrator is available by telephone or on the
Web.
If you live in the United States, you can call one of the following numbers:
v To order products or to obtain general information: 1-800-IBM-CALL
(1-800-426-2255)
v To order publications: 1-800-879-2755
Printed in USA
SC18-9162-02
Spine information: