Micro Focus Enterprise Developer 3.0 for Eclipse
>
Programming
>
Mainframe Programming
>
SQL Option for DB2
>
Reference
>
Error Messages
>
L - Link Error Messages
>
L700 - L799
L700 - L799
Lists the Link error messages from L700 through L799.
Restriction:
This topic applies to Windows environments only.
L713: REPLACEMENT VALUE value FOR special-register IS INVALID
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -713, for information.
L715: Prog program dep on function of the release from which fallback has occurred.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -715, for information.
L716: Program program precompiled with wrong level for this release.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -716, for information.
L717: object dependent on function of release from which fallback has occurred.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -717, for information.
L718: REBIND failed because IBMREQD of ibmreqd is invalid.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -718, for information.
L719: BIND ADD error, package package already exists.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -719, for information.
L720: Attempt to replace package package with existing version version.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -720, for information.
L721: BIND err CONTOK = contoken X cannot be created because it is not unique.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -721, for information.
L722: Package package does not exist.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -722, for information.
L723: ERROR IN TRIGGER trigger-name, SECTION NUMBER section-number
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -723, for information.
L724: ACTIVATION OF object-typeobject-name WOULD EXCEED MAXIMUM OF SQL CASCADING
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -724, for information.
L725: SPECIAL REGISTER register AT location WAS SUPPLIED INVALID VALUE
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -725, for information.
L726: Cannot replace package package. Enable or disable entries also with package.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -726, for information.
L728: DATA TYPE data-type IS NOT ALLOWED IN DB2 PRIVATE PROTOCOL PROCESSING
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -728, for information.
L729: COMMIT ON RETURN STORED PROCEDURE CANNOT BE IN NESTED CALL STATEMENT
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -729, for information.
L730: The parent of a table in a read-only database must also be in the database.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -730, for information.
L731: User-defined dataset dsname must be defined with SHAREOPTIONS(1,3).
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -731, for information.
L732: Table space or index space has not been defined on the owning subsystem.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -732, for information.
L733: The description of a table space, index space or ROSHARE READ db must be consistent.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -733, for information.
L734: The ROSHARE attr of a database cannot be altered from ROSHARE READ.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -734, for information.
L735: Database dbid is not longer a shared database.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -735, for information.
L736: Invalid OBID obid specified.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -736, for information.
L737: Implicit table space not allowed.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -737, for information.
L739: ALTER function-name FAILED; PARALLEL PROCESSED FUNCTIONS CANNOT MODIFY DATA
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -739, for information.
L740: FUNCTION name THAT MODIFIES SQL DATA IS NOT VALID IN CURRENT CONTEXT
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -740, for information.
L741: WORK FILE DATABASE IS ALREADY DEFINED FOR MEMBER member-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -741, for information.
L742: DSNDB07 IS THE IMPLICIT WORK FILE DATABASE
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -742, for information.
L746: SQL STATEMENT IN name VIOLATES THE NESTING SQL RESTRICTION
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -746, for information.
L747: table-name NOT AVAILABLE UNTIL AUX TABLES AND INDEXES HAVE BEEN CREATED
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -747, for information.
L748: AN INDEX ALREADY EXISTS ON AUXILIARY TABLE table-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -748, for information.
L750: TABLE source-name CANNOT BE RENAMED; REFERENCED BY EXISTING DEFINITIONS
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -750, for information.
L751: object-typeobject-name (specific-name) ATTEMPTED TO EXECUTE statement
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -751, for information.
L752: CONNECT statement invalid because the process is not in the connectable state.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -752, for information.
L763: INVALID TABLE SPACE NAME table-space-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -763, for information.
L764: LOB TABLE SPACE AND ITS BASE TABLE SPACE MUST BE IN SAME DATABASE
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -764, for information.
L765: TABLE IS NOT COMPATIBLE WITH DATABASE
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -765, for information.
L766: REQUESTED OPERATION NOT PERMITTED ON AUXILIARY TABLE OF STATEMENT OBJECT
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -766, for information.
L767: MISSING OR INVALID COLUMN SPECIFICATION FOR INDEX index-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -767, for information.
L768: AUXILIARY TABLE ALREADY EXISTS FOR THE SPECIFIED COLUMN OR PARTITION
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -768, for information.
L769: SPECIFICATION OF AUX TABLE DOES NOT MATCH CHARACTERISTICS OF BASE TABLE
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -769, for information.
L770: TABLE table-name CANNOT HAVE LOB COLUMN UNLESS IT ALSO HAS ROWID COLUMN
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -770, for information.
L771: INVALID SPECIFICATION OF A ROWID COLUMN
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -771, for information.
L797: ATTEMPT TO CREATE TRIGGER trigger-name WITH AN UNSUPPORTED SQL STATEMENT
L798: ATTEMPT TO INSERT VALUE INTO ROWID GENERATED ALWAYS COLUMN column-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -798, for information.
Parent topic:
L - Link Error Messages
