This appendix contains a list of DB2 RXSQL return codes and error messages. The return codes are returned in the REXX variable RC.
The following are the CMS return codes issued when DB2 RXSQL is not found or could not get through initialization.
| -3 |
Explanation: DB2 RXSQL was not found by CMS or RXSQL was called through an unsupported interface (for example, call RXSQL ...).
System Action: The program ends and the user is returned to CMS.
User Response: Link to the correct DB2 RXSQL production library.
| 28 | DMSSOP036E OPEN ERROR CODE '04' ON 'RXSQL '. |
Explanation: RXSQL LOADLIB was not found by RXSQL MODULE.
System Action: The program ends and the user is returned to CMS.
User Response: Ensure that the correct DB2 RXSQL production library is linked.
| 28 | DMSSOP036E OPEN ERROR CODE '04' ON 'ARISQLLD'. |
Explanation: ARISQLLD LOADLIB was not found by the DB2 Server for VM Resource Adapter.
System Action: The program ends and the user is returned to CMS.
User Response: Ensure that the DB2 Server for VM production library is linked.
| 41 | DMSFRE159T INSUFFICIENT STORAGE AVAILABLE TO SATISFY DMSFREE REQUEST FROM address. |
Explanation: There was not enough free storage to load the DB2 RXSQL code from the RXSQL LOADLIB. A minimum of approximately 500K bytes of free storage is needed.
System Action: The program ends and the user is returned to CMS.
User Response: Obtain more storage for your virtual machine and rerun the program.
The following are the return codes from a request where DB2 RXSQL had no error, but the DB2 Server for VM system gave an error or warning.
| -10 |
Explanation: DB2 Server for VM has issued a serious error as a result of the last database request. See the SQLCA variables.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check the returned SQLCODE variable and other SQLCA variables in your program and refer to DB2 Server for VM Messages and Codes manual for an explanation.
| 4 |
Explanation: DB2 Server for VM has issued a warning as a result of the last database request. See the SQLCA variables.
System Action: The DB2 RXSQL request was completed with warnings. Control is returned to the user's REXX program.
User Response: Check the returned SQLCODE variable and other SQLCA variables in your program and refer to DB2 Server for VM Messages and Codes manual for an explanation.
| 8 |
Explanation: DB2 Server for VM has issued a serious error as a result of the last database request. See the SQLCA variables.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check the returned SQLCODE variable and other SQLCA variables in your program and refer to DB2 Server for VM Messages and Codes manual for an explanation.
| 10 |
Explanation: DB2 Server for VM has issued a warning as a result of the last database request. See the SQLCA variables.
System Action: The DB2 RXSQL request was completed with warnings. Control is returned to the user's REXX program.
User Response: Check the returned SQLCODE variable and other SQLCA variables in your program
and refer to DB2 Server for VM Messages and Codes manual for an explanation.
In the following sections, the conventions for showing messages are:
In the explanation following the message text, the variables are in italics.
All RXSQL messages begin with a message identifier of the form ELOnnnnt, where:
Explanation contains information about the message, such as:
System Action describes the resulting action that was or will be taken by RXSQL.
User Response, Operator Response,
The following messages are issued when there is an RXSQL error. The return code will be less than -100 on EXECSQL invocation, and greater than 100 on RXSQL invocation.
| ELO0101E | Insufficient storage available to start DB2 RXSQL. |
Explanation: The attempt to start DB2 RXSQL failed because not enough storage could be obtained.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Obtain more storage for your virtual machine and rerun the program
| ELO0103E | Insufficient storage available for DB2 RXSQL to process the request. |
Explanation: The amount of storage DB2 RXSQL needs to process the request is not available.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Obtain more storage for your virtual machine and rerun the program.
| ELO0104E | Error trying to fetch or set a REXX variable. Return code from EXECOMM = -1. |
Explanation: An unexpected error was returned from EXECCOMM while DB2 RXSQL was trying to fetch or set a REXX variable.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: See the VM/ESA REXX/VM Reference manual for a description of the -1 return code from EXECCOMM and apply corrective measures.
| ELO0105E | The data type data_type_number of column col_number is not supported by DB2 RXSQL. |
Explanation: DB2 RXSQL did not recognize the data type of the column in position col_number. The number found in the SQLTYPE field of the SQLDA was data_type_number. DB2 RXSQL did not recognize the SQLTYPE supplied by the database manager in the SQLDA as one of the supported SQLTYPEs.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Make sure you are running compatible release levels of the database manager and DB2 RXSQL. Ensure that DB2 RXSQL supports all data types in the tables being accessed.
| ELO0106E | DB2 RXSQL Error code = code: invalid internal code used. |
Explanation: The DB2 RXSQL interface module to the database manager has received an invalid internal code.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Inform your DB2 RXSQL system programmer of the error.
System Programmer Response: Check that there are no inconsistencies with release levels of DB2 RXSQL. If there are none, contact IBM support with the problem.
| ELO0107E | DB2 RXSQL was not invoked from a REXX program. |
Explanation: The return code from EXECCOMM was -3. There was no EXECCOMM environment available. DB2 RXSQL was not called from a REXX program.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Refer to the VM/ESA REXX/VM Reference manual for a description of the -3 return code from EXECCOMM. Ensure that your program is a REXX program.
| ELO0108E | Invalid variable name name. |
Explanation: REXX rejected the request to set or fetch a variable because the name did not conform to REXX standards. Only the first 20 characters of your REXX variable name are shown. You may have had more main variables on the DB2 RXSQL request than DB2 RXSQL expected.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check the variable names on the request and ensure that they are valid REXX variables. Rerun the program.
| ELO0109E | Unexpected error trying to fetch or set a REXX variable. RC=hexadecimal_code. |
Explanation: An unexpected error was returned from EXECCOMM as a result of trying to fetch or set REXX variables. hexadecimal_code is the SHVRET value for an EXECCOMM call.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Refer to the VM/ESA REXX/VM Reference manual for a description of the return codes from EXECCOMM (SHVRET).
| ELO0110E | An error has occurred while trying to read GLOBALV variable name. |
Explanation: An error occurred when DB2 RXSQL tried to access the LASTING GLOBALV file. The LASTING GLOBALV file may be updated by the SQLINIT program and the CMS GLOBALV command. You did not invoke the SQLINIT program before using DB2 RXSQL, or you deleted a value from the LASTING GLOBALV file, or you placed an incorrect parameter in the LASTING GLOBALV file. The group name for values used by DB2 RXSQL is SQL/DS. DB2 RXSQL tried to access the global variable name.
If name was one of 'DATEFORMAT', 'TIMEFORMAT', 'LDATELEN' or 'LTIMELEN' then any date or time data fetched in subsequent requests will be returned in the ISO format. It is assumed that there are no local date and time exits.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Issue the SQLINIT program with the correct parameters. If the error persists, notify your system programmer.
System Programmer Response: Verify the parameters that were specified in the SQLGLOB program during initialization.
| ELO0111E | Unexpected error from EXECCOMM. Return code is negative. |
Explanation: An unexpected error was returned from EXECCOMM. DB2 RXSQL was trying to fetch or set a REXX variable. The EXECCOMM return code was negative but not recognized by DB2 RXSQL. (The return code is not equal to -1, -2 or -3)
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Refer to the VM/ESA REXX/VM Reference manual for a description of the negative return codes from EXECCOMM and apply corrective measures.
| ELO0115E | Insufficient storage was available to set REXX variables. |
Explanation: DB2 RXSQL was attempting to set a REXX variable value and EXECCOMM could not acquire enough storage to set the value. The return code from EXECCOMM was -2.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Obtain more storage for your virtual machine and rerun the program. For more information refer to the VM/ESA REXX/VM Reference manual for a description of the -2 return code from EXECCOMM.
| ELO0116E | name does not represent a SELECT statement. request request cannot be executed. |
Explanation: The statement name or prepare name specified in the request request does not refer to a prepared or declared SELECT statement.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check your spelling of the statement name and rerun the program.
| ELO0117E | name is not open. FETCH request cannot be executed. |
Explanation: The cursor name, prepare name or statement name, name, as an argument of the FETCH request has not been previously OPENed.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's program.
User Response: Issue an OPEN request using the cursor name or statement name, name, and then issue the FETCH.
| ELO0118E | name represents a SELECT statement. A PUT request cannot be executed. |
Explanation: The statement name or prepare name specified in a PUT request represents a SELECT statement.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check your spelling of the statement name and rerun the program.
| ELO0120E | An attempt was made to prepare more than the allowed limit of n statements. |
Explanation: No more than n SQL statements can be processed by the PREP request in a single program.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Issue a PURGE request for one or more of the existing statements, reuse a statement name in a PREPARE request, or use Extended Dynamic statements.
| ELO0129E | metavariable is an invalid function number. |
Explanation: The function metavariable following the TRACE command has specified a function number that is either not numeric or is not one of the valid function numbers.
System Action: The DB2 RXSQL request was executed successfully. Control is returned to the user's REXX program.
User Response: Check the function metavariable following the TRACE command, change it and rerun the program.
| ELO0130E | metavariable is an undefined trace level. |
Explanation: The trace metavariable following a TRACE command has specified a trace level that was not one of the valid levels.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check the trace metavariable following the TRACE command, change it and rerun the program.
| ELO0134E | Too many input rexx-host-variables were coded on the statement. |
Explanation: The statement contained too many rexx-host-variables in the input-rexx-host-variable-list to pass on to the database. The maximum number of input rexx-host-variables allowed is 32767.
System Action: The request has not executed successfully. The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Reduce the number of input rexx-host-variables and rerun your program. Note that the database manager may have a smaller limit than DB2 RXSQL and a further error could be produced by the database manager if its maximum is exceeded.
| ELO0135E | Section section of package package owned by creator is not a SELECT. Request was request. |
Explanation: The statement represented by the section number, creator name and package name on a request request is not a SELECT statement. The creator name may not be present if one was not given on the request.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Make sure that you are referencing the correct section in your package. Change the request and rerun your program.
| ELO0138E | name has a cursor-name cursor-name. request must use the cursor name. |
Explanation: A cursor for the statement associated with name exists. As a result, the DB2 RXSQL request must be issued with the cursor-name.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Change the request to use the cursor name, and rerun the program.
| ELO0139E | name is not OPEN - unable to operation. |
Explanation: A CLOSE or PUT request has been issued for an SQL statement that has not been previously processed by an OPEN request.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: An OPEN request must be issued before a CLOSE or PUT request can be performed. Change the program accordingly and rerun the program.
| ELO0142E | Name name has no associated dynamically prepared statement. |
Explanation: An operation was issued without providing a dynamically prepared SQL statement for the name name.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: You must issue a Dynamic PREPARE statement to assign a statement to the statement name you used in your request.
| ELO0143E | The name name is too long. |
Explanation: The cursor name, prepare name or statement name given is more than 18 characters long.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Shorten the statement name or cursor name shown to 18 characters or less. Rerun the program.
| ELO0144E | name is not valid. |
Explanation: The name specified for an SQL statement on a Dynamic PREPARE, Dynamic DECLARE or Extended DECLARE request contains an invalid character.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Refer to the DB2 REXX SQL for VM/ESA Installation and Reference manual for a description of valid cursor names, prepare names or statement names. Change the statement name to the allowed format and rerun the program.
| ELO0145E | The name name does not exist. |
Explanation: name has not been provided on any previous PREPARE or DECLARE statements. There is no SQL statement associated with name.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: A PREPARE or DECLARE request must be issued to define a statement name or cursor name and assign it to an SQL statement.
| ELO0149E | SQL statement of length len is too long. |
Explanation: The maximum length for an SQL statement is 32767 characters. If your cursor or statement name in the WHERE CURRENT OF clause is 1 or 2 characters long, DB2 RXSQL will expand your statement by up to 2 characters when it substitutes its own values for cursor or statement name before the request is passed to the database manager.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Reduce the size of your SQL statement. Rerun the program.
| ELO0150E | Value passed in position pos of length len is too long. |
Explanation: The maximum length for an SQL character string is 32767 characters.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Reduce the size of the character string. Rerun the program.
| ELO0151E | Operator command of length length is too long. |
Explanation: The maximum length for an operator command accepted by RXSQL is 80 characters.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Reduce the size of your operator command. Rerun the program.
| ELO0152E | Error in operator command processing. |
Explanation: The attempt to issue an operator command failed because the database returned unexpected information to DB2 RXSQL. The REXX SQLCA variables have been set.
System Action: The request has not executed successfully. The DB2 RXSQL request was not completed. Control is returned to the user's REXX program.
User Response: Check the SQLCA variables, correct the problem and rerun the program.
| ELO0154E | The name name in a Dynamic EXECUTE statement is associated with an Extended Dynamic statement. |
Explanation: The name name found in a Dynamic EXECUTE statement has been declared as a statement name for an extended dynamic statement. A statement name cannot be used in a Dynamic EXECUTE statement when it is already being used in an Extended Dynamic statement.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Correct the statement and rerun the request.
| ELO0156E | Work unit information could not be obtained. DMSCSL return code rc. |
Explanation: System information for the CMS work unit could not be obtained. No further processing can be done in this CMS work unit. If CMS work units were being used for the first time, no further processing can be done by the program.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Refer to the VM/ESA: CMS Application Development Reference manual for more information on the return code for the Callable Services Library Routines: DMSQWUID and DMSERP.
| ELO0163E | The parameter value value on the CONNECT request is too long. |
Explanation: The value for the specified parameter is too long.
System Action: The request has not executed successfully. The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Correct the input and rerun the program. See the DB2 REXX SQL for VM/ESA Installation and Reference manual for the details on the CONNECT statement.
| ELO0168E | The authorization name name is too long. |
Explanation: The authorization name (creator) must be a string of 1 to 8 characters.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Shorten the name and rerun the program.
| ELO0169E | Section number number is not in the valid integer range. |
Explanation: The section number provided was either negative, zero or greater than 2,147,483,647. A valid section number ranges from 1 to 2,147,483,647.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that your section number is in the valid range and rerun the program.
| ELO0170E | Name name matches the cursor name. |
Explanation: A cursor name and prepare name on a Dynamic DECLARE statement were identical.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Change either the cursor name or prepare name so that they are different. Make sure that all other requests using the old name are also changed. Rerun the program.
| ELO0171E | Cursor name cursor_name is already in use. |
Explanation: The cursor name cursor_name provided on a DECLARE statement is already defined for another statement. It matches either a cursor name or a prepare name.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: To reuse the name, issue an explicit PURGE request for the name. Otherwise, change the name and rerun the program.
| ELO0172E | The package id id is too long. |
Explanation: The package identifier id must be a string of 1 to 8 characters.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Shorten the name and rerun the program.
| ELO0173E | Non-numeric section number value. |
Explanation: The section number must be numeric.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that the value for the section number is numeric and rerun your program.
| ELO0174E | The name name is already in use. |
Explanation: The name name provided is already in use. It matches either a previously declared cursor name or a statement name.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: To reuse the name, issue an explicit PURGE request for the name. Otherwise, change the name and rerun the program.
| ELO0184E | Output is not supported on a dynamic request. |
Explanation: The INTO clause is not supported for the Extended Dynamic request that you issued. It is only supported for the Extended request for a SELECT statement you prepared into a package with the SINGLE ROW format.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Change your request by removing the INTO clause and rerun the program.
| ELO0187E | The syntax of the section number variable named section-var is invalid. |
Explanation: The section number variable name must start with a colon.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Correct the input and rerun the program.
| ELO0189E | The syntax of the statement variable named statement-var is invalid. |
Explanation: The statement variable name must start with a colon.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Correct the input and rerun the program.
| ELO0192E | Invalid date-time length value retrieved. Value was value. |
Explanation: DB2 RXSQL retrieved the local date or time length value (LDATELEN or LTIMELEN) from your LASTING GLOBALV file. Either the length is an invalid length (too large or too small) or an illegal character was encountered during conversion.
Any date or time data fetched in subsequent requests will be returned in the ISO format. It is assumed that there are no local date and time exits.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Issue the SQLINIT program with correct parameters. If the error persists, notify your system programmer.
System Programmer Response: Verify the parameters that were specified in the SQLGLOB EXEC during initialization.
| ELO0194E | date-time format is invalid. Value retrieved was value. |
Explanation: DB2 RXSQL fetched the DATEFORMAT or TIMEFORMAT from your LASTING GLOBALV file. An unrecognized value value was retrieved. Only the first 20 characters of the value are displayed.
Any date or time data fetched in subsequent requests will be returned in the ISO format. It is assumed that there are no local date and time exits.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Issue the SQLINIT program with correct parameters. If the error persists, notify your system programmer.
System Programmer Response: Verify the parameters that were specified in the SQLGLOB EXEC during initialization.
| ELO0195E | Unrecognized date-time data received from the database manager. Data was data. |
Explanation: DB2 RXSQL has received date or time data (data) from the database manager in a format that cannot be recognized. The data is not in any of the database manager date or time formats and the local date or time exit does not recognize the data. Only the first 20 characters of the actual data is given in the message.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Inform your DB2 RXSQL system programmer of the error.
System Programmer Response: Check that there are no inconsistencies with the local date or time exit. For example, the exit should recognize the same date or time formats on both input and output. Also, make sure that the same version of the local exit has been linked with both DB2 Server for VM and DB2 RXSQL modules. Correct the problem, link-edit DB2 RXSQL, and rerun the program.
| ELO0196E | Supplied local date-time exit not replaced by user's local exit. |
Explanation: DB2 RXSQL has tried to format a date or time value into the local format. However, the DB2 Server for VM local date or time exit was not replaced by a local exit when DB2 RXSQL was installed.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Inform your DB2 RXSQL system programmer of the error.
System Programmer Response: Make sure that the DB2 RXSQL link-edit was successful and that the correct local date or time exit is being linked with DB2 RXSQL. Re-link if necessary and rerun the program.
| ELO0197E | Invalid date-time value, function number = number, local exit RC = rc. |
Explanation: DB2 RXSQL has called the local date or time exit to format a value retrieved from the database manager. The local exit indicated that the date or time value was invalid or that the date or time value was not in a valid format (check the return code rc).
The function number number indicated the direction in which the conversion was being performed by the local exit. If the number was '4' then the data was being converted from the LOCAL format to the ISO format. If the number was '8' then the data was being converted from the ISO format to the LOCAL format.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Inform your DB2 RXSQL system programmer of the error.
System Programmer Response: Find out why the local date or time exit did not recognize the data format that was passed to it. Correct the problems with the local exit, link-edit DB2 RXSQL again, and rerun the program.
| ELO0198E | Error returned from local date-time exit. Function = func, rc = rc. |
Explanation: DB2 RXSQL has called the local date or time exit to perform the specified function, as indicated by func. The local exit returned the return code rc when trying to perform the operation.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Inform your DB2 RXSQL system programmer of the error.
System Programmer Response: Find out why an error occurred in the local date or time exit using the information returned in the message. Look at the function being performed and the return code from the routine. Correct the problems with the local exit, link-edit DB2 RXSQL again, and rerun the program.
| ELO0202E | Variable var is undefined or dropped. |
Explanation: The variable var was undefined. This variable must contain a value.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that the variable's value has been set. Change your program and rerun it.
| ELO0204E | main_variable is undefined and the value of indicator_variable was non-negative. |
Explanation: The main variable was undefined, yet the indicator variable indicated that the main variable would be set with a value.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check that the main variable or the indicator variable was set correctly or that the main variable was not inadvertently dropped. Change your program and rerun your program.
| ELO0209E | NULL data was retrieved for main variable main-var but no indicator variable was provided. |
Explanation: DB2 RXSQL was invoked using EXECSQL invocation. NULL data was retrieved from the database, yet no indicator variable was provided to indicate this. Indicator variables are compulsory when retrieving NULL data using EXECSQL invocation.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that indicator variables are provided for all columns which can contain NULL values in your select list.
| ELO0211E | The indicator variable ind_var is undefined. |
Explanation: The indicator variable did not have a value. DB2 RXSQL requires that an indicator variable, if provided, must have a value.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Assign a value to the indicator variable or remove the indicator variable from the statement. Rerun the program.
| ELO0213E | An indicator variable is required for main variable main-var to input NULL data. |
Explanation: DB2 RXSQL was invoked using EXECSQL invocation. The main variable provided was undefined and no indicator variable was provided. This is not allowed using EXECSQL invocation.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: If you wish to input NULL data to the database manager, you must provide an indicator variable and assign a negative value to the variable.
| ELO0214E | GRAPHIC data data in variable var has an odd number of bytes. |
Explanation: GRAPHIC data must have an even number of bytes.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check your GRAPHIC data to ensure that you have an even number of bytes. Rerun your program.
| ELO0215E | The value number in variable variable is out of the valid range for a floating point number. |
Explanation: The number was too small or too large to be represented as a floating point number for the target operating system.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that your data is within the range for your operating system and rerun the program.
| ELO0216E | An invalid floating point number number was in variable variable. |
Explanation: DB2 RXSQL did not recognize the number as a valid floating point number.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that your data is correct and rerun the program.
| ELO0217E | The value number you provided in variable is out of the range for SMALLINT. |
Explanation: The value is out of the valid range for a small integer for the target operating system.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that your column data type definition should be SMALLINT. If you really wish to insert this number, your column data type definition should be changed to INTEGER. Otherwise, ensure that your data is correct. Rerun your program.
| ELO0218E | The value number you provided in variable is out of the range for INTEGER. |
Explanation: The value is out of the valid range for an integer for the target operating system.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that your column data type definition should be INTEGER. If you really wish to insert this number, your column data type definition should be changed. Otherwise, ensure that your data is correct. Rerun your program.
| ELO0219E | The value number you provided for variable is an invalid integer. |
Explanation: DB2 RXSQL did not recognize the value number as a valid integer number.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that your data is correct and rerun the program.
| ELO0220E | The value number for variable variable is an invalid decimal number. |
Explanation: DB2 RXSQL did not recognize the value as a valid decimal number.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that your data is correct and rerun the program.
| ELO0221E | The value value for variable variable will result in high order truncation. |
Explanation: Significant high order digits will be truncated from your number with the precision and scale given.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that your data is correct or ensure that the precision and scale are correct for the column. Rerun the program.
| ELO0230E | The value of variable variable has an invalid character hex_value at position pos. |
Explanation: The variable value is invalid because it contains an invalid character.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Correct the request and rerun the program.
| ELO0232E | The value for the variable variable has a length of zero. |
Explanation: The REXX variable variable was an empty string. For the request you are executing, the variable must have a length greater than zero.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Assign a valid value to the variable and rerun the program.
| ELO0239E | name must be used instead of cursor-name for the request. |
Explanation: A cursor was declared for the statement associated with name, but the statement name or prepare name must be used for the request request.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Change the request to use the statement name, and rerun your program.
| ELO0241E | Initial state for name is invalid for the request. |
Explanation: The statement must be in one of the initial states listed for the request in the DB2 REXX SQL for VM/ESA Installation and Reference manual.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Make sure that the state of the statement is allowed for the request and rerun the program.
| ELO0242E | The variable var is an invalid stem variable. |
Explanation: A column and an indicator variable pair were provided, and only one of them is a valid stem variable.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Change the invalid variable name. Rerun your program.
| ELO0243E | Variable qualifiers are not allowed for stem variables. |
Explanation: A variable qualifier was provided for a stem variable. DB2 RXSQL does not allow this.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Remove the variable qualifier or change the variable name or names so that they don't look like stem variables. Rerun your program.
| ELO0250E | The CREATE PACKAGE options of length len are too long. |
Explanation: The maximum length for the options on a CREATE PACKAGE statement is 32767 characters. DB2 RXSQL appends the DESCRIBE option to the string that you specified, and this total length must not exceed the maximum.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Reduce the size of the options and rerun the program. Note that the database manager may have a smaller limit than DB2 RXSQL and a further error could be produced by the database manager if its maximum is exceeded.
| ELO0330E | The SQL statement has an invalid character, hex-value, at position pos. |
Explanation: The character found at the indicated position in the SQL statement is not a valid character.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Replace the character found with a valid character and rerun the request.
| ELO0340E | The request has an invalid character, hex-value, at position pos. |
Explanation: The character found at the indicated position in the request is not a valid character.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Replace the character found with a valid character and rerun the request.
| ELO0344E | The request begins properly but is incomplete. |
Explanation: The DB2 RXSQL request was correct up to the point where no more input was found.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check that the request is complete and rerun the program.
| ELO0345E | Syntax error detected at word word, position position in the request. |
Explanation: The word word is the first word that DB2 RXSQL does not recognize as being part of a valid request as shown in the DB2 RXSQL variable rxsqlrequest. This word may not be the cause of the error, it may be prior to this word.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check the value of rxsqlrequest, and correct the syntax of the request. Ensure that all keywords are spelled correctly. Rerun the program.
| ELO0350E | Invalid syntax at position position of the input string for request. |
Explanation: The syntax for the request was incorrect. The error occurred at or near position position relative to the first non-blank character of the input string. Look for misspelled keywords.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check the syntax of your request. Change the statement and rerun your program.
| ELO0444E | The variable list begins properly but is incomplete. |
Explanation: The variable list was correct up to the point where no more input was found.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check that the variable list is complete and rerun the program.
| ELO0445E | Syntax error detected at word word, position position in the variable list. |
Explanation: A syntax error has occurred in the variable list at word word. This word is position characters from the beginning of the variable list.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check the syntax of the variable list and rerun the program.
| ELO0450E | The field provided, value, is not valid. |
Explanation: On a variable qualifier, the value supplied was not correct for a field.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Change the value of the variable qualifier and rerun the request.
| ELO0500E | Unexpected C function error. File: file-name on Line: line-num detected the error. |
Explanation: A call to a C function returned with an error.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Contact your system programmer with all the accompanying information.
System Programmer Response: Contact your IBM Service representative for corrective measures. Be prepared to have the necessary information for the error.
| ELO0544E | The value of the attributes variable begins properly but is incomplete. |
Explanation: The value of the attributes variable was correct up to the point where no more input was found.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check that the value of the attributes variable is complete and rerun the program.
| ELO0545E | Syntax error detected at word word, position position in the attributes variable value. |
Explanation: A syntax error has occurred in the value of the attributes variable at word word. This word is position characters from the beginning of the value of the attributes variable.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Check the syntax of the value of the attributes variable and rerun the program.
| ELO0901E | A severe error occurred. Extra info: text File: file-name Line: line-num |
Explanation: DB2 RXSQL has discovered an internal inconsistency. file-name and line-num identify the DB2 RXSQL module that discovered the error. text may be provided to indicate more information about the error.
System Action: The DB2 RXSQL request was not executed successfully. Control is returned to the user's REXX program.
User Response: Contact your system programmer with all the accompanying information.
System Programmer Response: Contact your IBM Service representative for corrective measures. Be prepared to have the necessary information for the error.
| ELO0960E | Error trying to initialize the environment for DB2 RXSQL. |
Explanation: The attempt to start DB2 RXSQL failed in subcommand processing.
System Action: The DB2 RXSQL request has not executed successfully. Control is returned to the user's REXX program.
User Response: This could be due to shortage of storage. Obtain more storage for your virtual machine and rerun the program. If the error persists, contact your system programmer with all the accompanying information.
System Programmer Response: Contact your IBM Service representative for corrective measures. Be prepared to have the necessary information for the error.
| ELO0961E | Error trying to initialize the environment for DB2 RXSQL. |
Explanation: The attempt to start DB2 RXSQL failed in inter-language setup.
System Action: The DB2 RXSQL request has not executed successfully. Control is returned to the user's REXX program.
User Response: This could be due to shortage of storage. Obtain more storage for your virtual machine and rerun the program. If the error persists, contact your system programmer with all the accompanying information.
System Programmer Response: Contact your IBM Service representative for corrective measures. Be prepared to have the necessary information for the error.
| ELO0962E | Error trying to initialize the environment for DB2 RXSQL. |
Explanation: The attempt to start DB2 RXSQL failed when trying to determine the operating environment.
System Action: The DB2 RXSQL request has not executed successfully. Control is returned to the user's REXX program.
User Response: Ensure that DB2 RXSQL is running on an operating system that is supported for DB2 RXSQL. If it is, contact your system programmer with all the accompanying information.
System Programmer Response: Contact your IBM Service representative for corrective measures. Be prepared to have the necessary information for the error.
| ELO0963E | Error trying to initialize the environment for DB2 RXSQL. |
Explanation: The attempt to start DB2 RXSQL failed when trying setup the environment for DB2 RXSQL.
System Action: The DB2 RXSQL request has not executed successfully. Control is returned to the user's REXX program.
User Response: Contact your system programmer with all the accompanying information.
System Programmer Response: Contact your IBM Service representative for corrective measures. Be
prepared to have the necessary information for the error.
The following messages are only issued on EXECSQL invocation, and indicate that RXSQL has issued a warning. The return code is always greater than 1000.
| ELO1136I | The statement for name was forced into a prepared or declared state during request processing. |
Explanation: The statement corresponding to name was not in a prepared or declared state. One of the following SQL statements was executed to force a prepared or declared state: CLOSE, Dynamic PREPARE or Extended DECLARE.
System Action: A warning has been issued. The DB2 RXSQL request was completed. Control is returned to the user's REXX program.
User Response: You may continue processing. To avoid this warning, issue the appropriate request in order to put the statement associated with name in a Dynamic PREPARED or Extended Dynamic DECLARED state.
| ELO1138I | The input data on the OPEN request for name was ignored. |
Explanation: An OPEN request for the cursor or statement named name has a variable list, however the statement corresponding to name is not a statement for which input is valid. As a result, the input has been ignored.
System Action: A warning has been issued. The DB2 RXSQL request was completed. Control is returned to the user's REXX program.
User Response: You may continue processing. To avoid this warning, remove the extra parameters on the OPEN request.
| ELO1140I | A Dynamic DECLARE has already been issued. |
Explanation: A Dynamic DECLARE was issued when a Dynamic DECLARE had already been done for the cursor name and statement name. A Dynamic DECLARE is not necessary in this instance and should be removed from your program to improve the performance of your program.
System Action: A warning has been issued. The DB2 RXSQL request was completed. Control is returned to the user's REXX program.
User Response: You may continue processing. To avoid this warning, remove the redundant DECLARE request from your program.
| ELO1142I | number variables were given, but there are select_number select-list columns. |
Explanation: The number of main variables in the REXX host variable list does not match the number of select-list expressions for the select statement.
System Action: A warning has been issued. The DB2 RXSQL request was completed. The number of REXX variables set with the data retrieved from the database is the minimum of number and select_number. Control is returned to the user's REXX program.
User Response: You may continue processing. To avoid this warning, the number of REXX variables to receive the fetched data must match the number of select-list columns.
| ELO1170I | An Extended Dynamic DECLARE has already been issued. |
Explanation: An Extended Dynamic DECLARE was issued when an Extended Dynamic DECLARE had already been done for the cursor name, section number and package name supplied. An Extended Dynamic DECLARE is not necessary in this instance and should be removed from your program to improve the performance of your program.
System Action: A warning has been issued. The DB2 RXSQL request was completed. Control is returned to the user's REXX program.
User Response: You may continue processing. To avoid this warning, remove the redundant DECLARE request from your program.
| ELO1175I | The attributes-variable specified on the Temporary Extended PREPARE was ignored. |
Explanation: A Temporary Extended PREPARE with an attributes variable was issued to fill an empty section. This attributes variable was ignored because it is ignored by the database manager.
System Action: A warning has been issued. The DB2 RXSQL request was completed. Control is returned to the user's REXX program.
User Response: You may continue processing. To avoid this warning, remove the USING clause from the Extended Dynamic PREPARE request.
| ELO1221I | The value for variable variable will result in low order truncation. |
Explanation: Low order digits will be truncated from your number with the precision and scale given for the column.
System Action: A warning has been issued. The DB2 RXSQL request was completed. Control is returned to the user's REXX program.
User Response: You may continue processing.
| ELO1299I | PUT was reissued after database error. SQLSTATE=sqlstate, SQLERRD1=sqlerrd1, SQLERRD2=sqlerrd2. |
Explanation: A PUT request was rejected by the database manager because the data type or length has changed for a main variable whose ordinal position was sqlerrd2 in the REXX host variable list. DB2 RXSQL has intercepted this error from the database manager, has issued an SQL CLOSE and OPEN, and has reissued the PUT.
System Action: A warning has been issued. The DB2 RXSQL request was completed. Control is returned to the user's REXX program.
User Response: You may continue processing. To avoid this warning, ensure that all the
data you are inserting into column number sqlerrd2 looks like the
same data type and has the same length. You may alternately provide
variable qualifiers on your PUT statement that defines the target
column's data type.
The following messages are issued only from the DB2 RXSQL-supplied programs.
| ELO2100E | XMITMSG RC= rc. |
Explanation: An error occurred when a message from the DB2 RXSQL message repository was being retrieved. XMITMSG ended with a return code of rc.
System Action: No further processing is done. Control is returned to the user. The system waits for the user.
User Response: Refer to any other system messages that may have occurred. If the return code was 16 and a message was displayed saying the ELO repository was not found, then enter 'SET LANGUAGE (ADD ELO USER' to load the DB2 RXSQL message repository. For other errors refer to the VM/ESA: System Messages and Codes manual for the proper user response.
| ELO2101E | Invalid or conflicting fn ft parameter(s). |
Explanation: The parameters used for the fn ft EXEC were not recognized or resulted in conflicting actions.
System Action: The operation was not executed successfully. Control is returned to CMS.
User Response: Refer to the section in the VM/ESA REXX/VM Reference manual describing the fn ft parameters allowed on the invocation.
| ELO2102I | *** DB2 RXSQL Version num1 Release num2 Modification num3 *** |
Explanation: Identifies the DB2 RXSQL version and release modification level the user is invoking.
System Action: Normal completion. The user is returned to CMS.
| ELO2111E | type text is not installed or database is not available. |
Explanation: The HELP text was not available at the time of invocation. Either the appropriate tables were not installed, not available, or the database was not available.
System Action: The operation was not executed successfully. Control is returned to CMS.
User Response: Refer to the SQLCA variables for more information. Ensure that the database is available and that the HELP table(s) indicated in the SQLCA variables have been created. If the HELP table(s) have been installed, the table(s) may have been temporarily unavailable. Try again later.
| ELO2112I | type text is not available for topic topic for language langkey. |
Explanation: |The operation was not executed successfully. There was no DB2 |RXSQL or DB2 Server for VM HELP text for the topic topic, in the |language indicated by langkey.
System Action: |If this message is issued after RXSQL HELP |topic, then processing continues with SQL/DS HELP |topic. If this message is issued after SQL/DS |HELP topic, then processing ends and control is returned to |CMS.
User Response: If the topic was an ELO or ARI message ID, ensure that you entered all of the numbers in that message ID. If the topic was an unsigned number, a positive number is assumed. If you wanted HELP for a negative number, place a minus (-) sign before the number.
| ELO2121I | ******** End-of-Data ********** |
Explanation: This is an informational message put at the end of the file being XEDITed. It indicates that all data from the query has been retrieved.
System Action: You are at the bottom of the file in XEDIT. The system waits for you to enter the next command.
| ELO2122I | Enter MORE to display more rows of data. |
Explanation: Informational message indicating that there is more data to be retrieved and written to the file.
System Action: The system waits for you to enter the next command.
User Response: Enter MORE in the command line to get more rows of data into the file being XEDITed.
| ELO2123I | Enter RXSQLHLP topic to get more information. |
Explanation: More information on the topic given may be retrieved by entering RXSQLHLP topic on the command line.
System Action: The system waits for you to enter the next command.
User Response: Enter 'RXSQLHLP topic' on the command line, if you wish to get more information on the topic.
| ELO2124I | Line truncated num characters by EXECIO. |
Explanation: The row retrieved was too long to put in the file. Num indicates the number of characters that were truncated while writing to the file.
System Action: The truncated row was inserted in the file. The system continues writing rows into the file.
| ELO2131I | Current setting is case. |
Explanation: The current case setting used by the RXSELECT EXEC is case. If case is UPPER, the SQL statement will be converted to upper case before being sent to the database manager. If the case is STRING, the statement will be sent to the database manager as it was entered.
System Action: The command was completed and the user is returned to CMS. The system waits for the next command.
| ELO2141I | No 'WHERE' clause was used on cmd statement. |
Explanation: No 'WHERE' clause was specified on your cmd statement. More rows may have been affected than was intended.
System Action: The command was completed with warnings. The system waits for the next command.
User Response: You should verify that the change was intended unconditionally on the entire table. Refer to other messages issued and take action as indicated by those messages.
| ELO2142I | Row count = num. |
Explanation: Num represents the number of rows processed by the command.
System Action: The command was completed with warnings. The system waits for the next command.
User Response: Check the row count against what you expected the number of affected rows to be. Refer to other messages displayed for more information and for an action to be taken. Also refer to SQLERRD.3 description in DB2 Server for VSE & VM Application Programming manual.
| ELO2143I | Row count = num1 , Dependent row count = num2. |
Explanation: Num1 represents the number of rows processed by the command. Num2 represents the number of dependent rows affected when the object table is a part of a referential structure.
System Action: The command was completed with warnings. The system waits for the next command.
User Response: Check the row counts against what you expected the number of affected rows to be. Refer to other messages displayed for more information and for an action to be taken. Also refer to SQLERRD.3 and SQLERRD.5 descriptions in DB2 Server for VSE & VM Application Programming manual.
| ELO2144I | Enter ROLLBACK or CANCEL to cancel the changes done. |
Explanation: The system is waiting for a ROLLBACK or CANCEL response. If neither is entered, a COMMIT will be performed.
System Action: The system waits for a response from the user.
User Response: If you wish to rollback the changes made in this LUW, then enter ROLLBACK or CANCEL. Otherwise, press enter to commit all changes made so far.
| ELO2151E | Operator commands may not be issued while in a logical unit of work. |
Explanation: You are in a logical unit of work. Operator commands are not allowed while you are in a LUW.
System Action: The operator command was not executed. The system waits for the user to enter a command.
User Response: Refer to other messages issued and take action as indicated by those messages.
| ELO2152I | Do a COMMIT or ROLLBACK and try the command again. |
Explanation: Enter COMMIT or ROLLBACK on the command line. If you wish to keep all changes made thus far, enter COMMIT; otherwise, enter ROLLBACK.
System Action: The system waits for the user to enter a command.
User Response: Issue a COMMIT or ROLLBACK to end the current LUW. Rerun the command.
| ELO2153E | Operator commands may not be issued while in single-user-mode. |
Explanation: You are in single-user-mode. Operator commands are not allowed while you are in single-user-mode.
System Action: The operator command was not executed. The system waits for the user to enter a command.
User Response: Do not issue operator commands while in single-user-mode. Restart the database in multiple user mode if you wish to enter operator commands.
| ELO2154E | Error processing DB2 Server for VM operator commands. |
Explanation: An error was encountered while executing the DB2 Server for VM operator command.
System Action: The operator command was not executed. The system waits for the user to enter a command.
User Response: Refer to other messages issued and take action as indicated by those messages.
| ELO2155E | Invalid SHOW command. |
Explanation: The SHOW command you entered was invalid.
System Action: The operator command was not executed. The system waits for the user to enter a command.
User Response: Refer to the DB2 Server for VSE & VM Operation manual for more information on the correct usage of the SHOW command. Change the command and rerun the program. Refer to any other messages issued and take action as suggested.
| ELO2156E | Invalid DB2 Server for VM operator command. |
Explanation: The operator command entered was not a valid DB2 Server for VM operator command.
System Action: The operator command was not executed. The system waits for the user to enter a command.
User Response: Refer to other messages issued and take action as indicated by those messages.
| ELO2157E | No DB2 Server for VM operator command entered. |
Explanation: There was no DB2 Server for VM operator command entered.
System Action: The operator command was not executed. The system waits for the user to enter a command.
User Response: Refer to other messages issued and take action as indicated by those messages.
| ELO2158E | DB2 Server for VM operator command value too long. |
Explanation: A value entered with the operator command was too long.
System Action: The operator command was not executed. The system waits for the user to enter a command.
User Response: Refer to other messages issued and take action as indicated by those messages.
| ELO2159E | Invalid operator command. |
Explanation: The operator command entered was not a valid operator command.
System Action: The operator command was not executed. The system waits for the user to enter a command.
User Response: Refer to the DB2 Server for VSE & VM Operation manual for more information on operator commands. Change the command as necessary and rerun the program.
| ELO2160E | The CMS GLOBALV command failed. The return code from GLOBALV was rc. |
Explanation: An error occurred when an attempt was made to update the LASTING GLOBALV file. GLOBALV ended with a return code of rc.
System Action: No further processing is done. Control is returned to the user. The system waits for the user.
User Response: Refer to the VM/ESA: CMS Command Reference manual for the proper user response.
| ELO2161E | The language language was not found in the table table. |
Explanation: language was not found in the LANGUAGE or LANGID column of table. This national language is not installed.
System Action: No further processing is done. Control is returned to the user. The system waits for the user.
User Response: Query table to determine which languages are installed.