Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Code Debug for Db2 Extension Run-Time Messages


Message codes

Description

SQI435 = 1,

COMMAND NOT RECOGNIZED

Explanation: The line command entered is not recognized as a valid command.

User Response: Check for a misspelled line command.

SQI435 = 2,

ONLY D, F, and L COMMANDS ARE PERMITTED ON EXCLUDED LINES

Explanation: The line command entered is not permitted on excluded lines.

User Response: Check for a misspelled line command.

SQI435 = 3,

NUMBER NOT ALLOWED WITH SPECIFIED LINE COMMAND

Explanation: A number is not allowed with the specified line command.

User Response: Remove the number, or enter another line command.

SQI435 = 4,

COMMAND NOT ALLOWED ON LINE

Explanation: The line command was entered on a non-Procedure Division line.

User Response: Remove the line command.

SQI435 = 5,

COMMAND NOT PERMITTED FOR DISPLAY ONLY LINE

Explanation: A line command was entered on a display-only line.

User Response: Check whether the command is entered for the correct line, or entered for a line that was optimized out.

SQI435 = 6,

INVALID SQL STATEMENT FOR EXPLAIN

Explanation: An SQL EXPLAIN command was entered on a line that does not contain a legal SQL statement.

User Response: Check whether the command was entered for the correct line, or is missing an SQL statement terminator, semicolon, or END-EXEC.

SQI479 = 1,

BLOCK COMMAND INCOMPLETE

Explanation: A matching block command was not entered.

User Response: Enter a matching block command to complete the block command pair.

SQIC00 = 1,

INVALID SET COMMAND

Explanation: The SET processor could not identify the category for the SET command.

User Response: None.

SQIC00 = 4,

ERROR PROCESSING SET COMMAND

Explanation: The SET command was unable to obtain the information needed to process; i.e., no parsed command block.

User Response: None.

SQIC00 = 97,

COMMAND BLOCK NOT FOUND

Explanation: The SET command was unable to obtain the parsed command block.

User Response: None.

SQIC00 = 98,

ENTERING SET FUNCTION

Explanation: The SET command is being invoked.

User Response: None.

SQIC00 = 99,

EXITING SET FUNCTION

Explanation: The SET command is being terminated.

User Response: None.

SQIDCI = 2,

MORE THAN 256 LEADING BLANKS ON SQL STATEMENT

Explanation: There are more than 256 blanks preceding the SQL verb.

User Response: Make sure that your SQL verb is entered within the first 256 bytes.

SQIDCI = 3,

OPEN FAILED ON SQLIN DATA SET

Explanation: An OPEN for the SQLIN data set failed.

User Response: Make sure you have allocated the data set—SQLIN is a sequential data set with an LRECL of 80.

SQIDCI = 4,

 INTERNAL ERROR

Explanation: An invalid request was made to SQIDCI. This is an internal error.

User Response: None.

SQID00 = 1,

KEYWORD CURSOR EXPECTED IN SQL STATEMENT, NONE PROVIDED

Explanation: The keyword CURSOR was expected in the SQL statement, and none was provided.

User Response: None.

SQID00 = 2,

SELECT PORTION ON DECLARE CURSOR STATEMENT MISSING

User Response: Check for the keyword SELECT.

SQID00 = 3,

CURSOR_NAME NOT SPECIFIED

Explanation: The CURSOR_NAME was expected in the SQL statement and none was provided.

User Response: None.

SQID00 = 4,

NO HOST VARIABLE(S) NOR DESCRIPTOR SPECIFIED

Explanation: Parameter markers were present in the SQL statement.

User Response: These must be resolved by supplying host variables or an SQLDA in the SQL call.

SQID00 = 5,

ADDRESS OF THE SQLDA_NAME CANNOT BE LOCATED

Explanation: You have supplied an SQLDA in the OPEN statement but its address could not be located in your program.

User Response: Check for spelling errors.

SQID00 = 6,

STATEMENT_NAME NOT SPECIFIED

Explanation: The STATEMENT_NAME was not specified on a PREPARE SQL call.

User Response: None.

SQID00 = 7,

ADDRESS OF THE SQLSOURCE CANNOT BE LOCATED

Explanation: The address of the SQLSOURCE on a PREPARE call cannot be located.

User Response: None.

SQID00 = 8,

SQL VERB IS NOT KNOWN TO CODE DEBUG FOR DB2 EXTENSION

Explanation: The SQL verb is not known to Code Debug for Db2 Extension.

User Response: Check for a spelling error.

SQID00 = 9,

KEYWORD DESCRIPTOR MISSING

Explanation: The keyword DESCRIPTOR on the SQL call is missing.

User Response: None.

SQID00 = 21,

ATTEMPTING TO USE MORE THAN 10 CURSORS

Explanation: You are attempting to use more than 10 internally defined SQL cursors.

User Response: You should free up a cursor by closing it.

SQID00 = 30,

COMMIT NOT EXECUTED BECAUSE AT LEAST ONE CURSOR OPEN

Explanation: The COMMIT was not executed because at least one dynamic cursor was open. Normally, the COMMIT would close the cursor, and any reference to it from the program would return a user -514 SQLCODE.

User Response: None.

SQID00 = 101,

SQL STATEMENT TOO LONG. CODE DEBUG FOR DB2 EXTENSION ALLOWS UP TO 12,288 BYTES

Explanation: Your SQL statement exceeds the maximum permissible length of 12,288, internally set by Code Debug for Db2 Extension. Code Debug for Db2 Extension expands your SQL call by filling in the values of host variables. If the expanded length is greater than 12,288 bytes, you will also get this error.

User Response: Reduce the original length by eliminating unnecessary blanks.

SQID00 = 102,

SQL VERB NOT KNOWN TO CODE DEBUG FOR DB2 EXTENSION

Explanation: The SQL verb is not known. Leading blanks are allowed, but a blank line without a verb is flagged with this error code.

User Response: Check for a spelling error.

SQID01 = 4,

NO “INTO” OR HOST VARIABLE FOUND

Explanation: The SQL statement requires either an INTO clause or at least one host variable. Neither of these was found in the SQL statement.

User Response: None.

SQID01 = 5,

HOST VARIABLE NOT DEFINED IN PROGRAM

Explanation: A host variable was referenced in the SQL statement. However, its address could not be resolved using the DDIO data set.

User Response: Check for spelling errors.

SQID01 = 6,

INDICATOR VAR. NOT DEFINED IN PROG.

Explanation: An indicator variable was referenced in the SQL statement. However, its address could not be resolved using the DDIO data set.

User Response: Check for spelling errors.

SQID01 = 8,

HOST VARIABLE NOT RESOLVED. INVALID DATA TYPE

Explanation: The address of the host variable could not be resolved using the DDIO data set—invalid data type.

SQID01 = 9,

INVALID DBCREG

Explanation: An invalid request was made to ADSQID01. This is an internal error.

User Response: None.

SQID02 = 21,

REQUEST FUNCTION NOT KNOWN (INTERNAL ERROR)

Explanation: This is an internal error.

User Response: Contact BMC Support.

SQID02 = 22, 

DATATYPE IN SQLDA NOT KNOWN

Explanation: This is an internal error.

User Response: Contact BMC Support.

SQID02 = 23,

NO STORAGE TO OBTAIN. SQLD PROBABLY SET TO ZERO

Explanation: This is an internal error.

User Response: Contact BMC Support.

SQID20 = 1,

SQLDA IS IN ERROR, SQLD=0

Explanation: The SQLDA field has a zero value. This should not occur.

User Response: Contact BMC Support.

SQID20 = 2,

 DATATYPE REQUIRES ONE OR MORE INDICATOR VARIABLES

Explanation: One or more columns is defined to contain null values. However, no corresponding indicator variable was included in the SQL statement.

User Response: None.

SQIF00 = 1,

INVALID PRIMARY COMMAND

Explanation: A primary command of the format =x was entered, but x is not a valid option. Valid options are the characters/digits associated with Code Debug for Db2 Extension functions on the Primary Menu.

User Response: None.

SQIG00 = 1,

NO ROWS TO DISPLAY

Explanation: No rows were found to display.

User Response: None.

SQIG01 = 1,

INVALID COMMAND

Explanation: An invalid command or option was entered.

User Response: Check for a misspelled command and reenter.

SQIG01 = 2,

 INVALID LINE COMMAND ENTERED

Explanation: The line command entered is not recognized as a valid command.

User Response: Check for a misspelled line command.

SQIP00 = 1,

PROFILE NOT AVAILABLE

Explanation: The TSQLPROFILES table could not be read during Code Debug for Db2 Extension INIT time. Either you do not have authority to perform at least a SELECT on a table, or a timeout occurred.

User Response: Try getting to the TSQLPROFILES table through option 0. An SQL return code gives the exact reason for denial of access.

SQIRD0 = 1,

INVALID COMMAND

Explanation: An invalid command or option was entered.

User Response: Check for a misspelled command or option and reenter.

SQIRD0 = 2,

SQL ERROR

Explanation: An SQL error occurred.

User Response: Contact your internal technical support.

SQIRD0 = 3,

NO MORE ROWS TO FETCH

Explanation: No more rows were found to fetch.

User Response: None.

SQIR00 = 1,

INVALID COMMAND/OPTION ENTERED

Explanation: An invalid command or option was entered.

User Response: Check for a misspelled command or option and reenter.

SQIR00 = 2,

ERROR IN SELECT + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Select.

User Response: Contact your internal technical support.

SQIR00 = 3,

ERROR IN DELETE + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Delete.

User Response: Contact your internal technical support.

SQIR00 = 4,

ERROR IN PRINT + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Print.

User Response: Contact your internal technical support.

SQIR00 = 5,

ERROR IN BROWSE + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Browse.

User Response: Contact your internal technical support.

SQIR00 = 6,

INVALID LINE COMMAND ENTERED

Explanation: An invalid line command was entered.

User Response: Check for the misspelled command and reenter.

SQIR03 = 1,

ERROR IN SELECT + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Select.

User Response: Contact your internal technical support.

SQIR03 = 2,

ERROR IN DELETE + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Delete.

User Response: Contact your internal technical support.

SQIR03 = 3,

ERROR IN PRINT + DB2 ERROR MESSAGE

Explanation: An SQL error occurred in Report Print.

User Response: Contact your internal technical support.

SQIR03 = 4,

INVALID LINE COMMAND ENTERED

Explanation: An invalid line command was entered.

User Response: Check for the misspelled command and reenter.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*