Micro Focus Enterprise Developer 3.0 for Visual Studio 2017
>
Programming
>
Mainframe Programming
>
SQL Option for DB2
>
Reference
>
Error Messages
>
L - Link Error Messages
>
L900 - L999
L900 - L999
Lists the Link error messages from L900 through L999.
L900: Cannot EXEC SQL because application is not connected to application server.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -900, for information.
L901: System error caused failed execution so subsequent SQL may be successful.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -901, for information.
L902: Pointer to the essential ctrl block (CT/RDA) has value 0, rebind required.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -902, for information.
L904: Unavailable resource caused failed exec. type type of resource name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -904, for information.
L905: Fail exec due to resource limit, resource name name limit amount.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -905, for information.
L906: Cannot execute SQL statement. Function disabled due to a prior error.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -906, for information.
L907: Unable to determine if commit of updates made at a remote site failed.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -907, for information.
L908: bind error using authid authority no bind or rebind are allowed.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -908, for information.
L909: The object has been deleted.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -909, for information.
L910: SQL statement cannot access object on which a drop/alter is pending.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -910, for information.
L911: Rollback due to a deadlock/timeout. Reason code.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -911, for information.
L913: Failed execution cause by deadlock/timeout. Reason code code.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -913, for information.
L917: Bind package failed.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -917, for information.
L918: SQL cannot be executed because connection has been lost.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -918, for information.
L919: A ROLLBACK OPERATION IS REQUIRED
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -919, for information.
L922: AUTHORIZATION FAILURE: error-type ERROR. REASON reason-code
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -922, for information.
L923: CONNECTION NOT ESTABLISHED: DB2 condition REASON reason-code, TYPE resource-type, NAME resource-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -923, for information.
L924: DB2 CONNECTION INTERNAL ERROR, function-code, return-code, reason-code
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -924, for information.
L925: Commit not valid in IMS/VS or CICS environment.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -925, for information.
L926: Rollback not valid in IMS/VS or CICS environment.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -926, for information.
L927: Language interface called when the connecting environment was not established.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -927, for information.
L929: FAILURE IN A DATA CAPTURE EXIT: token
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -929, for information.
L939: ROLLBACK REQUIRED DUE TO UNREQUESTED ROLLBACK OF A REMOTE SERVER
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -939, for information.
L947: STATEMENT FAILED;WILL CHANGE TABLE DEFINED BUT DATA CANNOT BE PROPAGATED
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -947, for information.
L948: DISTRIBUTED OPERATION IS INVALID
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -948, for information.
L950: Location name is invalid or not in comm db.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -950, for information.
L981: STATEMENT FAILED;CONNECTION DOES NOT ALLOW SQL OPERATIONS, REASON reason-code.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -981, for information.
L991: CrossAccess Data Access error ErrorNum (ConditionCode) for IMS/VSAM. Consult CrossAccess System Messages documentation.
CrossAccess experienced the specified data error while processing an SQL request against IMS/VSAM. For additional information about this error, see your CrossAccess User Documentation.
L992: CrossAccess System error ErrorNum while accessing IMS/VSAM. Contact mainframe systems programming.
CrossAccess has experienced the specified system error while attempting to access IMS/VSAM. For additional information about this error, see your CrossAccess User Documentation.
Parent topic:
L - Link Error Messages
