Micro Focus Enterprise Developer 3.0 for Eclipse
>
Programming
>
Mainframe Programming
>
SQL Option for DB2
>
Reference
>
Error Messages
>
L - Link Error Messages
>
L500 - L549
L500 - L549
Lists the Link error messages from L500 through L549.
Restriction:
This topic applies to Windows environments only.
L500: IDENTIFIED CURSOR WAS CLOSED WHEN THE CONNECTION WAS DESTROYED
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -500, for information.
L501: Cursor identified in a FETCH or CLOSE statement is not open.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -501, for information.
L502: The cursor identified in an OPEN statement is already open.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -502, for information.
L503: Column cannot be updated because it is not in the UPDATE clause of the select.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -503, for information.
L504: The cursor name name is not defined.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -504, for information.
L507: The cursor identified in the UPDATE or DELETE statement is not open.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -507, for information.
L508: Cursor identified in an update or delete is not positioned on a row.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -508, for information.
L509: The table in an UPDATE or DELETE is not a table designated by cursor.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -509, for information.
L510: Table designated by cursor of UPDATE/DELETE statement cannot be modified.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -510, for information.
L511: FOR UPDATE clause invalid because cursor cannot be modified.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -511, for information.
L512: Statement reference to remote object is invalid.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -512, for information.
L513: The alias name must not be defined by another local or remote alias.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -513, for information.
L514: The cursor name is not in a prepared state.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -514, for information.
L516: The described statement does not identify a prepared statement.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -516, for information.
L517: Cursor name does not identify a prepared SELECT statement.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -517, for information.
L518: The EXECUTE statement does not identify a valid prepared statement.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -518 for information.
L519: PREPARE identifies SELECT statement of the open cursor name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -519, for information.
L525: SQL cannot execute, error at bind for section sectno, package pkgname, consistency token Xcontoken.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -519, for information.
L526: REQUESTED FUNCTION DOES NOT APPLY TO GLOBAL TEMPORARY TABLES
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -526, for information.
L530: The INSERT or UPDATE value of foreign key name is invalid.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -530, for information.
L531: Primary key in parent has dependent rows in relation name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -531, for information.
L532: The relation name restricts the deletion of row with RID X number.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -532, for information.
L533: Invalid multiple-row insert.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -533, for information.
L534: The primary key cannot be updated because of multiple-row update.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -534, for information.
L535: Invalid update or delete with WHERE CURRENT OF.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -535, for information.
L536: Delete is invalid because table name can be affected by the operation.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -536, for information.
L537: Primary key/foreign key identifies column name more than once.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -537, for information.
L538: Foreign key name does not match description of primary key of table name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -538, for information.
L539: Table name does not have a primary key.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -539, for information.
L540: Definition of table name does not have primary index.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -540, for information.
L541: FOREIGN KEY key-name HAS DUPLICATE REFERENTIAL CONSTRAINT
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -541, for information.
L542: name cannot be a column of primary key because it can contain NULL values.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -542, for information.
L543: CANNOT DELETE ROW IN PARENT TABLE; RESTRICTED BY CONSTRAINT check-constraint
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -543, for information.
L544: CANNOT ADD CHECK CONSTRAINT; EXISTING ROW VIOLATES THE CHECK CONSTRAINT
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -544, for information.
L545: The requested operation is not allowed because of the check constraint CheckConstraint.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -545, for information.
L546: CHECK CONSTRAINT constraint-name IS INVALID
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -159, for information.
L548: A CHECK CONSTRAINT THAT IS DEFINED WITH column-name IS INVALID
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -548, for information.
L549: The Statement statement is not allowed for ObjectType1ObjectName because the bind option dynamicrules in the ObjectType2 is in effect.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -549, for information.
Parent topic:
L - Link Error Messages
